> For the complete documentation index, see [llms.txt](https://docs.rome.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rome.builders/canton-zk-evm/evm-differences.md).

# Differences from Ethereum

Where Ostia's EVM differs from Ethereum, for contracts and tools. PREVRANDAO, beacon root, blob transactions, block time, finality, gas limits, Osaka, the standard contracts and nonce rules.

Ostia runs EVM contracts under Ethereum's rules up to Osaka, and the same tools work on it. A few things are not the same as on Ethereum or on a chain with a beacon chain behind it. Read this page before you rely on any of them. The values below were read from the public code and from the live RPC on 2026-11-11, with read-only calls.

| What                                           | On Ostia DevNet                                                                                                                         |
| ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| `block.prevrandao` and `block.difficulty`      | Always 0.                                                                                                                               |
| Beacon block root (EIP-4788)                   | Always 0.                                                                                                                               |
| Blob transactions (type 3)                     | Not supported. Do not send them.                                                                                                        |
| Time between blocks                            | Irregular: a median of about 28 s and a 95th percentile of about 59 s over the 24 hours to 2026-11-11.                                  |
| Finality                                       | The RPC shows only final blocks. A block is final about 10 s after it is cut (median); a receipt usually takes 10 to 30 s from sending. |
| Gas                                            | A block holds up to 60,000,000 gas. One transaction may use at most 2^24 (16,777,216).                                                  |
| `block.coinbase`                               | Always `0x0000000000000000000000000000000000000fee`.                                                                                    |
| CREATE2 deployer, Multicall3, CreateX, Permit2 | At their usual addresses since 2026-11-12. The Safe singleton factory is not deployed.                                                  |
| A nonce above the next one                     | Refused.                                                                                                                                |

## Randomness: `block.prevrandao` is 0

Ostia has no beacon chain, so there is no randomness source in a block. The builder sets `prevRandao` to zero in every block, and a live block's `mixHash` is `0x00…00`. In a contract, `block.prevrandao` and `block.difficulty` are a constant 0. A lottery, an NFT reveal or a game that reads them deploys and runs, but always gets 0. Do not use them. Use commit and reveal, or an oracle.

## The beacon root is 0

The parent beacon block root in every block header is zero, so the EIP-4788 contract (at `0x000F3df6D732807Ef1319fB7B8bB8522d0Beac02`, present from genesis) holds zero roots. Do not use it to prove anything about a beacon chain.

## No blob transactions

Ostia builds blocks with no blob support. Blob transactions (EIP-4844, type 3) are not supported, so do not send them. The `BLOBBASEFEE` and `BLOBHASH` opcodes exist because the chain runs Cancun and later, but there are no blobs, and the blob base fee shows its minimum of 1. `eth_blobBaseFee` is not one of the [20 methods](https://docs.rome.builders/canton-zk-evm/devnet.md#limits) that the RPC answers.

## Block time and finality

Ostia makes a block as soon as transactions wait, and an empty block once a minute when none do (see [a quiet chain](https://docs.rome.builders/canton-zk-evm/devnet.md#a-quiet-chain-makes-a-block-a-minute)). So blocks come at irregular gaps. Over the 24 hours to 2026-11-11, the median gap was about 28 s and the 95th percentile about 59 s. A contract that is tuned for 12-second Ethereum slots or 2-second rollup slots will behave differently. Read time from `block.timestamp`, which is in seconds and always at least one second past the parent's, and do not count blocks as time.

The RPC shows only blocks that are final on Canton. `latest`, `safe`, `pending` and `finalized` all mean the newest final block (except `eth_getTransactionCount` with `pending`, which counts waiting transactions), and `eth_call` runs against it. A receipt appears when its block is final: about 10 s after the block is made at the median and about 14 s at the 95th percentile, over the same 24 hours, after a wait for the block to be cut. The RPC shows no reorgs. The figures are on the explorer's `/api/stats/summary`.

## Gas and fees

The block gas limit is 60,000,000. Osaka caps one transaction at 2^24 gas, and the transaction pool refuses a transaction above it. The base fee is tiny (7 wei in the blocks read), and the gas price the RPC suggests is about 1 gwei. The fee recipient is fixed: every block's `block.coinbase` is `0x0000000000000000000000000000000000000fee`.

## What Osaka means here

Ostia has run Osaka since 2026-10-28 at 12:00 UTC, and a new local chain started from the repository's genesis runs it from its first block. In practice:

* one transaction may use at most 2^24 gas (EIP-7825);
* the `CLZ` opcode and the `P256VERIFY` precompile work (a contract that uses both was deployed and is final);
* code built for any EVM target up to `osaka` is accepted. An opcode added after Osaka will not run. `london` is a safe target.

The system contracts of Cancun and Prague are in the genesis. The EIP-2935 contract holds recent block hashes, as on Ethereum. The EIP-4788 contract holds zero roots, because there is no beacon chain. Requests to the EIP-7002 and EIP-7251 contracts have no effect beyond the fee they charge, for the same reason.

## The standard contracts

Four contracts that many tools expect at fixed addresses are on Ostia DevNet, deployed on 2026-11-12 (blocks 61159 to 61165), at their usual addresses and with the code their authors published:

| Contract         | Address                                      | What it is                                                                                                                                                    |
| ---------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| CREATE2 deployer | `0x4e59b44847b379578588920cA78FbF26c0B4956C` | The deterministic deployer: a call with a salt and init code deploys the contract at an address that follows from them. `forge script` with a `salt` uses it. |
| Multicall3       | `0xcA11bde05977b3631167028862bE2a173976CA11` | Batches many calls into one `eth_call` or transaction. viem's `multicall` and wagmi's batched reads use it.                                                   |
| CreateX          | `0xba5Ed099633D3B313e4D5F7bdc1305d3c28ba5Ed` | A factory for `CREATE`, `CREATE2` and `CREATE3` deployments.                                                                                                  |
| Permit2          | `0x000000000022D473030F116dDEE9F6B43aC78BA3` | Signature-based token approvals and transfers, one approval per token for every app that uses it.                                                             |

The Safe singleton factory, `0x914d7Fec6aaC8cd542e72Bca78B30650d45643d7`, is not deployed: `eth_getCode` returns empty code there, so tools that expect it at that address do not find it. Check with `eth_getCode` before you rely on any of these, because DevNet may be reset (see [Ostia DevNet](https://docs.rome.builders/canton-zk-evm/devnet.md#devnet-may-be-reset)).

## Nonces and the order of sends

A transaction whose nonce is above the account's next one is refused as a nonce gap, where an Ethereum node would hold it in a queue. Send one account's transactions in order, one after another. A script that sends several at once can have them arrive in a different order, and the later one is refused. With Foundry scripts, add `--slow`, which sends each transaction after the previous one is confirmed.

## Methods

The RPC answers 20 methods and no others. There are no `debug_` or `trace_` methods, no filters, no `eth_subscribe` and no WebSocket. [Ostia DevNet](https://docs.rome.builders/canton-zk-evm/devnet.md#limits) lists them and the limits.

## A reset keeps the chain id

If DevNet is reset, the new chain has the same chain id, 770101. See [DevNet may be reset](https://docs.rome.builders/canton-zk-evm/devnet.md#devnet-may-be-reset) for what that means for signed transactions and your tools' saved state.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rome.builders/canton-zk-evm/evm-differences.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
