> For the complete documentation index, see [llms.txt](https://docs.valuechain.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valuechain.xyz/3.-evm-system-chain.md). # 3. EVM System Chain #### 3.1 Role of the EVM system chain The EVM system chain has two jobs: 1. **Shared system state and general-purpose execution.** It manages the overall system state of ValueChain and fully supports EVM-compatible applications. Solidity and Vyper contracts, standard wallets and standard developer tools work without changes (see 6.2 to 6.7). 2. **The unified account layer for all appchains.** A user's ValueChain EVM address is their identity across the whole network. Appchain balances belong to that address. As a result, every appchain stays interoperable with the wider EVM ecosystem. #### 3.2 Execution environment * **Hard fork.** The execution layer matches Ethereum's **Pectra** revision, except for blob transactions. * **Accepted transaction types.** Legacy (type 0), access-list (type 1) and EIP-1559 (type 2) transactions are accepted. * **Rejected transaction types.** Blob-carrying transactions (EIP-4844, type 3) are rejected. Blob data should never be assumed available. * **Tooling.** Wallets, RPC clients and Solidity/Vyper toolchains work as on other EVM chains: Foundry, Hardhat, Remix, Ethers.js and Viem. * **Addresses.** A contract's address on Ethereum is not its address on ValueChain. Always identify tokens and protocol contracts by their ValueChain address. #### 3.3 Gas and fees * **Gas token.** Gas is paid in **native SOSO** (18 decimals), not ETH. * **No ERC-20 form for native SOSO.** Native SOSO has no ERC-20 address. Neither WSOSO nor any other ERC-20 balance can pay gas. * **EIP-1559 without burning.** EIP-1559 is enabled, but **the base fee is not burned**. The base fee and the priority fee both go to the block builder. * **Effective price per gas:**\ effectiveGasPrice = min(maxFeePerGas, baseFeePerGas + maxPriorityFeePerGas)execution fee (SOSO) = gasUsed × effectiveGasPrice / 10^18\ For example, 21,000 gas at 2,000,000 wei per gas costs 0.000000042 SOSO. That puts routine transactions at very low cost. #### 3.4 Finality semantics in JSON-RPC ValueChain's block tags follow its finality model, not Ethereum's. | Tag | Meaning on ValueChain | | ---------------- | ------------------------------------------------------------------------------------------------------------------- | | latest | Current head. Inclusion is already irreversible. | | safe / finalized | Same block for both. It is a checkpoint that usually lags latest by one slot (about 2 s), not an extra safety wait. | | pending | The proposed next block. | | earliest | Genesis. | A transaction receipt with a block number means the transaction is **included and final**. Receipt `status` reports only the EVM outcome. When an application settles on an appchain, its own status must also be checked. #### 3.5 System contracts | Contract | Address | Purpose | | ----------- | ------------------------------------------ | ----------------------------------------------------------------------------------------------------------- | | WSOSO | 0x5050505050505050505050505050505050505050 | Canonical wrapped SOSO. It is immutable and uses the same code as WETH apart from name and symbol. | | ClobGateway | 0x0101010101010101010101010101010101010101 | Moves assets from the EVM into the Spot and Perps trading appchains and handles trading-account operations. | Standard infrastructure contracts are already deployed: * **ERC-4337 account abstraction:** EntryPoint v0.6–v0.9 and Simple7702Account. * **Safe v1.4.1:** including the 4337 and Passkey (WebAuthn) modules. * **Multicall3.** Full addresses are in Appendix B. #### 3.6 Transaction Relayer: sponsored gas ValueChain offers a **Transaction Relayer**, so applications can pay gas on behalf of their users. * **How to use it.** An approved integration submits a target contract and ABI-encoded calldata. The Relayer broadcasts the call and pays the SOSO gas. * **Who the sender is.** On chain, `msg.sender` is the Relayer wallet. Actions taken on a user's behalf must carry the user's own authorization, such as a permit or an `onBehalf` signature. * **Access.** Integrations are registered and their target contracts allow-listed. Submissions are rate-limited per source IP: 2 per second, 10 per 5 minutes and 50 per hour by default. * **Availability.** The Relayer is on mainnet only. Together with account abstraction (ERC-4337 and EIP-7702), the Relayer lets applications offer gas-free experiences. SoDEX's gas-free trading is one example. #### 3.7 Developer access
MainnetTestnet
Chain ID286623 (0x45f9f)138565 (0x21d45)
HTTP RPChttps://mainnet.valuechain.xyzhttps://testnet.valuechain.xyz
WebSocketwss://mainnet-ws.valuechain.xyzwss://testnet-ws.valuechain.xyz
Explorerhttps://main-scan.valuechain.xyzhttps://test-scan.valuechain.xyz
The explorer is Blockscout-compatible, so contracts can be verified directly from Foundry. The JSON-RPC interface follows the standard Ethereum Execution API, including `eth_simulateV1` and WebSocket subscriptions (Appendix C).