# Divergence from Ethereum

While Bitroot features full EVM compatibility, there are some distinctions between Bitroot’s EVM and Ethereum itself.

#### EVM Differences <a href="#evm-differences" id="evm-differences"></a>

***

Unlike Ethereum mainnet which is on Cancun for its execution layer, Bitroot uses the Shanghai version of EVM. This means that features like blob transactions are not supported on Bitroot.

#### Opcode Differences <a href="#opcode-differences" id="opcode-differences"></a>

***

**PREVRANDAO**

Since Bitroot doesn’t rely on the same pseudo-randomness way of determining the next validator like Proof of Stake (PoS) Ethereum does, it doesn’t really have the `RANDOM` artifact that can be set as `PREVRANDO`’s return value. In Bitroot `PREVRANDAO` is set to return the hash of the current block time. For strong randomness guarantee needs in contracts logic, it’s advised to use external verifiable oracles (as is advised on Ethereum itself).

**COINBASE**

Coinbase address on Bitroot is always set to (the EVM address of) the global fee collector.

#### State Root <a href="#state-root" id="state-root"></a>

***

Since Bitroot uses AVL-tree instead of Merkle Patricia Trie (MPT) for data storage, Bitroot doesn’t have per-account state root. The global state root is the AVL-tree root which is also not equivalent to Ethereum’s overall state root (which is a MPT root)

#### Block Hash <a href="#block-hash" id="block-hash"></a>

***

The block hash on Bitroot is computed based on the block header in Tendermint data format, and is different from Ethereum’s block Hash as a result.

#### Block Limit <a href="#block-limit" id="block-limit"></a>

***

Bitroot has a gas limit of 10M on `pacific-1`, compared to Ethereum’s 30M.

In addition, Bitroot also has a byte size limit of 21MB, whereas Ethereum doesn’t have byte-denominated limits.

#### Non-EVM Transactions <a href="#non-evm-transactions" id="non-evm-transactions"></a>

***

On Bitroot there exists non-EVM transactions which may update states accessible by EVM transactions. The simplest example would be bank balances, which may be updated by both native Cosmos bank send transactions and EVM send transactions. As a result, if certain offchain applications only parse EVM transactions, they may find certain state changes unattributable to any EVM transaction.

#### Finality <a href="#finality" id="finality"></a>

***

Bitroot has instant finality, meaning that commitment levels of “safe”, “latest”, “justified”, and “finalized” on Ethereum are all the same thing on Bitroot.

#### Pending State <a href="#pending-state" id="pending-state"></a>

***

On Ethereum the block proposer would execute its proposed block first (and update its local state) before broadcasting the proposal to others (the updated state would be marked “pending” until the node is accepted by other nodes).

However, on Bitroot, the block proposer would broadcast first and only execute the proposal if it’s accepted (i.e. every node would execute the block at roughly the same time), so Bitroot does not really have a window when “pending state” exists.


---

# Agent Instructions: 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:

```
GET https://bitroot.gitbook.io/bitroot/divergence-from-ethereum.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.