> For the complete documentation index, see [llms.txt](https://sodex.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sodex.com/documentation/about-valuechain/how-valuechain-works/about-valuechain-evm.md).

# About ValueChain EVM

The EVM syschain manages the overall system state of ValueChain and provides full support for all EVM-compatible dApps. Beyond that, it also acts as the unified account system for other appchains, ensuring that every appchain remains interoperable with the broader EVM ecosystem. Each appchain, in turn, maintains the transactions and state of its dedicated application, enabling deterministic and high-performance execution. SOSO is the native gas token on the EVM syschain.

Note that there are currently no official frontend components of the EVM. Users can build their own frontends or port over existing EVM applications. All interaction with the EVM happens through the JSON-RPC. For example, users can add the chain to their wallets by entering the RPC URL and chain ID.

The EVM syschain uses the Pectra hardfork without blobs. In particular, EIP-1559 is enabled on the EVM syschain. Unlike standard implementation of EIP-1559, the base fees are not burned and instead sent together with priority fees to block builder.

On both mainnet and testnet, SOSO on the EVM syschain has 18 decimals. A few differences between testnet and mainnet are highlighted below:

* Mainnet
  * Chain ID: `286623`
  * JSON RPC endpoint: `https://mainnet.valuechain.xyz`
  * Websocket endpoint: `wss://mainnet-ws.valuechain.xyz`
  * Explorer: `https://main-scan.valuechain.xyz`
* Testnet
  * Chain ID: `138565`
  * JSON RPC endpoint: `https://testnet-v2.valuechain.xyz`
  * Websocket endpoint: `wss://testnet-v2-ws.valuechain.xyz`
  * Explorer: `https://test-scan.valuechain.xyz`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sodex.com/documentation/about-valuechain/how-valuechain-works/about-valuechain-evm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.