> 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/network/architecture/nexusevm.md).

# NexusEVM

NexusEVM is the EVM execution layer of the Nexus blockchain. 1-second blocks with single-slot finality.

#### EVM compatibility

* Same bytecode — no Nexus-specific compiler flags
* Same gas semantics — all 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

#### Developer experience

Deploy using Hardhat, Foundry, or Remix. Use 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. When NexusCore launches, it will handle exchange functions at a faster block cadence. The two layers will interoperate, allowing any EVM contract to compose 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/network/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.