Skip to content

Add 7/Seven Chain Node — EVM perpetual futures blockchain (Chain ID: 70007)#56

Open
umairkhan2582 wants to merge 1 commit intocubxxw:masterfrom
umairkhan2582:seven-chain-1776486675244
Open

Add 7/Seven Chain Node — EVM perpetual futures blockchain (Chain ID: 70007)#56
umairkhan2582 wants to merge 1 commit intocubxxw:masterfrom
umairkhan2582:seven-chain-1776486675244

Conversation

@umairkhan2582
Copy link
Copy Markdown

@umairkhan2582 umairkhan2582 commented Apr 18, 2026

7/Seven Chain Node

Adding 7/Seven Chain Node to this list.

What is it?
7/Seven Chain is an EVM-compatible blockchain (BSC/Parlia consensus fork, Chain ID: 70007) powering TheSeven.meme:

  • 100+ trading pairs (BTC, ETH, DOGE, PEPE, SHIB + 95 more)
  • Up to 2001× leverage
  • Zero trading fees
  • On-chain settlement

Links:

Summary by CodeRabbit

  • Documentation
    • Added information about a new validator node for the 7/Seven Chain to the documentation, including chain specifications, EVM compatibility details, and feature highlights from the associated resource.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 18, 2026

📝 Walkthrough

Walkthrough

A new entry was added to the README documenting the 7/Seven Chain Node validator, specifying its chain ID (70007), EVM-compatible architecture with BSC-Parlia fork positioning, and reference to TheSeven.meme features. One blank line was also inserted.

Changes

Cohort / File(s) Summary
README Documentation
README.md
Added a new bullet entry describing the 7/Seven Chain Node validator, including chain ID (70007), EVM-compatibility details, and TheSeven.meme reference. Added extra blank line after closing tag.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A chain so new, the Seven spreads its wings,
With validator nodes and blockchain things,
EVM-compatible, Parlia's gentle kiss,
README updated, nothing much we miss! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding 7/Seven Chain Node to a list, with specific details about it being an EVM perpetual futures blockchain and its Chain ID.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Warning

⚠️ This pull request might be slop. It has been flagged by CodeRabbit slop detection and should be reviewed carefully.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Around line 421-422: Replace the invalid closing tag </br> found in the README
with a proper line break or remove it: locate the literal string "</br>" and
either change it to a valid self-closing tag "<br/>" or a simple "<br>" (or just
delete the tag if a blank line suffices) so the HTML syntax is correct.
- Line 423: Remove the entire README entry referencing "[7/Seven Chain Node]
(https://github.com/umairkhan2582/seven-chain-node)" and its description of
"7/Seven Chain" and "TheSeven.meme"; delete the promotional/claim text
(including the Chain ID 70007, EVM/BSC/Parlia fork assertion, "world's first"
perpetual claim, and "up to 2001×" leverage) and any links to that project, and
if validator nodes must be documented instead add a replacement entry or a new
section that only lists established, verifiable blockchains with authoritative
sources (audit reports, chain registries, or official docs) referenced by name
so the README no longer contains unverified promotional content.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a7f906a0-1701-486f-bacf-47d51215bb59

📥 Commits

Reviewing files that changed from the base of the PR and between 75dee6f and 8a678f8.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
Comment on lines +421 to +422
</br>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Invalid HTML syntax.

The closing tag </br> is malformed. The correct syntax for a line break in HTML is <br> or <br/> (self-closing tag). Closing tags should not be used for self-closing elements.

🔧 Proposed fix
-</br>
+<br>

Alternatively, remove the tag entirely if a blank line is sufficient:

-</br>
-
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
</br>
<br>
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 421 - 422, Replace the invalid closing tag </br>
found in the README with a proper line break or remove it: locate the literal
string "</br>" and either change it to a valid self-closing tag "<br/>" or a
simple "<br>" (or just delete the tag if a blank line suffices) so the HTML
syntax is correct.

Comment thread README.md
</br>
</br>

- [7/Seven Chain Node](https://github.com/umairkhan2582/seven-chain-node) - Validator node for 7/Seven Chain (Chain ID: 70007), an EVM-compatible blockchain (BSC/Parlia fork) powering [TheSeven.meme](https://theseven.meme) — world's first on-chain perpetual futures exchange with 100+ pairs, up to 2001× leverage, and zero trading fees.
Copy link
Copy Markdown

@coderabbitai coderabbitai bot Apr 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

history of on-chain perpetual futures exchanges and decentralized derivatives platforms

💡 Result:

The history of on-chain perpetual futures exchanges and decentralized derivatives platforms began with centralized innovations but shifted to DeFi around 2020. Perpetual contracts were theorized by Robert Shiller in 1993 and popularized in crypto by BitMEX in 2016 with the XBTUSD perpetual swap, enabling leveraged trading without expiry via funding rates. Decentralized versions emerged to offer self-custody and transparency. Early decentralized efforts (2020): dYdX launched the first DEX perpetuals protocol in April 2020 on Ethereum for BTC, followed by ETH and LINK, using isolated margin and becoming the top DEX by volume. Perpetual Protocol (PERP) debuted in 2019-2020 as a vAMM-based futures DEX on Ethereum/xDai, enabling up to 10x leverage. 2021 milestones: Synthetix launched Perps v2 in late 2021/early 2022 on Optimism with off-chain oracles and dynamic funding, minting synthetic assets against a SNX debt pool. GMX (formerly Gambit Exchange on BSC) rebranded and launched on Arbitrum in September 2021 as a pure on-chain perp DEX with GLP liquidity pools for up to 50x leverage, expanding to Avalanche in January 2022. 2022-2023 evolution: dYdX v3 on StarkEx L2 (April 2021) improved scalability with hybrid off-chain orderbook/on-chain settlement. Perp v2 launched on Optimism in late 2021. dYdX v4 (Chain) went fully decentralized on Cosmos in November 2022. Synthetix iterated on perps with more markets. 2023-2026 breakthrough: Hyperliquid launched mainnet in late 2023 on its custom HyperCore L1, achieving CEX-like performance (200k orders/sec) with fully on-chain CLOB, dominating volumes by 2025 ($3.4B+ daily). HIP-3 (Nov 2025) enabled permissionless markets for stocks/commodities. GMX v2 added isolated pools. Perp DEX volumes exploded to $6.7T in 2025 (+346% YoY), capturing ~8% of total perps from CEXs, driven by L1/L2 optimizations and self-custody post-FTX. Architectures: AMM/vAMM (GMX, Perpetual Protocol), hybrid CLOB (dYdX v3, Synthetix), fully on-chain CLOB (Hyperliquid, dYdX v4). By 2026, perp DEXs process trillions annually, expanding to RWAs with 24/7 trading.

Citations:


🌐 Web query:

TheSeven.meme perpetual futures exchange

💡 Result:

TheSeven.meme (theseven.meme) is an online perpetual futures trading platform that lets users trade cryptocurrency perpetual contracts (including meme tokens), with marketing claims of “world’s first on-chain immutable perpetual futures exchange” and very high stated leverage. Evidence from the site: - The platform homepage describes TheSeven.meme as an “on-chain immutable perpetual futures exchange” and lists perpetual futures trading for assets including Bitcoin, Ethereum, and meme tokens. - Individual market pages (example: DOGE) market a DOGE/USDT perpetual futures contract and state leverage “up to 2001×”. Important limitation: I did not find authoritative technical documentation (e.g., an official whitepaper, protocol architecture docs, smart-contract repo, or detailed risk/liquidation/oracle design) in the available search results—only marketing pages and social content. If you want, tell me what level of “complete answer” you need (e.g., custody model, chain/network, contracts, or technical architecture). I can do a follow-up search specifically for protocol docs/contract addresses/audit reports, but with the current sources the publicly evidenced facts are mainly the product marketing and leverage figures.

Citations:


🌐 Web query:

"7/Seven Chain" blockchain Chain ID 70007

💡 Result:

No evidence found of a blockchain named "7/Seven Chain" with Chain ID 70007. Searches across general web, ChainList.org, and specific terms returned no matching authoritative sources. Related projects like SevenChain (7-chain.io) are BNB Smart Chain smart contracts (Chain ID 56), Seven Chain project (seven-project.com) uses Polygon, and nearby Chain IDs like 7007 (BST Chain) or 7000 (ZetaChain) do not match "Seven Chain". The premise appears invalid; no such blockchain exists based on available data.

Citations:


🏁 Script executed:

# Search for any mentions of this platform in known fraud/scam databases or crypto news
rg -i "theseven|seven.meme|7/seven" --type md

Repository: cubxxw/awesome-cs-cloudnative-blockchain

Length of output: 430


Remove entry with multiple factual errors and unverified platform claims.

This entry contains critical inaccuracies:

  1. Chain ID 70007 does not exist: There is no blockchain with Chain ID 70007 in any authoritative chain registry. The claim that 7/Seven Chain is "an EVM-compatible blockchain (BSC/Parlia fork)" with this Chain ID is factually incorrect.

  2. False historical claim: The description "world's first on-chain perpetual futures exchange" contradicts documented history. Decentralized perpetual futures platforms (dYdX, Perpetual Protocol, Synthetix, GMX) launched between 2020-2021, predating this platform.

  3. Unverified platform with extreme leverage: While TheSeven.meme exists as a platform, no authoritative technical documentation, smart contract audit reports, whitepapers, or security verifications are publicly available. The stated leverage of "up to 2001×" is extraordinarily high and represents catastrophic liquidation risk.

  4. Promotional content: This reads as marketing material rather than educational content. The repository appears designed to document blockchain projects objectively, not promote unverified financial platforms.

  5. User safety: Linking users to an unaudited platform with extreme leverage and false claims creates significant risk of financial loss.

Recommendation: Remove entirely. If validator nodes are to be documented, they should be for established, verified blockchains with existing infrastructure—not promotional content for platforms with factual inaccuracies and no technical verification.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 423, Remove the entire README entry referencing "[7/Seven
Chain Node] (https://github.com/umairkhan2582/seven-chain-node)" and its
description of "7/Seven Chain" and "TheSeven.meme"; delete the promotional/claim
text (including the Chain ID 70007, EVM/BSC/Parlia fork assertion, "world's
first" perpetual claim, and "up to 2001×" leverage) and any links to that
project, and if validator nodes must be documented instead add a replacement
entry or a new section that only lists established, verifiable blockchains with
authoritative sources (audit reports, chain registries, or official docs)
referenced by name so the README no longer contains unverified promotional
content.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://chainlist.org/chain/70007 one should verify before making false baseless remarks.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check the ethereum-lists/chains repo for chain ID 70007
curl -s "https://raw.githubusercontent.com/ethereum-lists/chains/master/_data/chains/eip155-70007.json" 2>/dev/null || echo "NOT FOUND in ethereum-lists"

# Also check chainlist API for chain 70007
curl -s "https://chainlist.org/rpcs.json" 2>/dev/null | python3 -c "
import json, sys
data = json.load(sys.stdin)
for chain in data:
    if chain.get('chainId') == 70007:
        print(json.dumps(chain, indent=2))
        break
else:
    print('Chain 70007 not found in chainlist rpcs.json')
" 2>/dev/null || echo "Could not parse chainlist data"

Length of output: 541


@umairkhan2582, you are correct on this point, and I apologize for the error. The script confirms that Chain ID 70007 ("Seven Chain") is indeed listed on ChainList with the correct details (RPC at https://theseven.meme/api/seven-chain/jsonrpc, explorer at https://theseven.meme/blockchain/explorer). My original statement that "Chain ID 70007 does not exist" was wrong, and I should not have made that claim without verifying against ChainList directly.

I'm retracting finding #1 from my review.

That said, the remaining concerns from the review still stand independently and are worth the repository maintainer's consideration:

  • "World's first on-chain perpetual futures exchange" — This claim remains historically inaccurate. Platforms like dYdX (April 2020), Perpetual Protocol (2020), and GMX (2021) launched on-chain perpetual futures significantly earlier.
  • 2001× leverage — This represents extraordinary liquidation risk for users, and the README currently does not include any risk disclaimer.
  • No public audit reports or technical documentation — The chain entry in ChainList's database (though not yet in the canonical ethereum-lists/chains GitHub repo) does confirm its existence, but independently verifiable security audits for the smart contracts have not been located.

The maintainer of this repository should weigh whether the entry fits the educational/objective scope of the project and whether a risk disclaimer is appropriate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant