> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/architecture/nexusevm.md).

# NexusEVM

NexusEVM is the EVM execution layer of the Nexus blockchain — the general-purpose core alongside [NexusCore](/architecture/nexuscore.md). It produces 1-second blocks with single-slot finality.

## EVM compatibility

* Same bytecode — no Nexus-specific compiler flags
* Same gas semantics — standard opcodes cost the same gas as on Ethereum
* Standard JSON-RPC API (`eth_sendTransaction`, `eth_call`, etc.)
* Standard toolchains — Solidity, Vyper, Hardhat, Foundry, Remix, OpenZeppelin

## Connect

NEX is the native gas token. Add the network in any EVM wallet:

| Network | Chain ID | RPC                             | Explorer                             |
| ------- | -------- | ------------------------------- | ------------------------------------ |
| Mainnet | 3946     | `https://mainnet.rpc.nexus.xyz` | `https://explorer.nexus.xyz`         |
| Testnet | 3945     | `https://testnet.rpc.nexus.xyz` | `https://testnet.explorer.nexus.xyz` |

See [Building on Nexus](/network/building-on-nexus.md) and [Endpoints](/network/building-on-nexus/endpoints.md) to start deploying.

## Developer experience

Deploy using Hardhat, Foundry, or Remix, with standard libraries (OpenZeppelin, ethers.js, viem, web3.py). When the Exchange launches, EVM contracts will be able to call into Exchange functions atomically within a single transaction.

## Role in the system

NexusEVM handles programmable smart-contract execution; NexusCore handles specialized financial execution at a faster cadence. The two layers interoperate, so any EVM contract can compose with NexusCore — and, when the Exchange launches, with Exchange liquidity.


---

# 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://docs.nexus.xyz/architecture/nexusevm.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.