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

# Differences from Ethereum

Nagara aims to behave like Ethereum for contract developers. These are the places where it does not.

## Precompiles

Available:

* `0x01` ecrecover
* `0x02` sha256
* `0x03` ripemd160
* `0x04` identity
* `0x05` modexp
* `0x0400` SHA3-FIPS256
* `0x0401` ecrecover returning the public key
* `0x0402` Curve25519 point addition
* `0x0403` Curve25519 scalar multiplication

**Not available:** `0x06`–`0x08` (BN254 add, mul, pairing), `0x09` (BLAKE2f), `0x0a` (KZG point evaluation), and the BLS12-381 precompiles.

{% hint style="danger" %}
Calling a missing precompile does **not** revert. The address holds no code, so the call succeeds and returns empty data. Contracts that check only the call's success flag will silently misbehave. In particular, standard Groth16 and PLONK verifiers (which rely on BN254 pairing) will not work on Nagara.
{% endhint %}

## Gas and fees

* The gas price is set by an EIP-1559 base fee and currently sits around **4,762 gwei**. That is much higher than on Ethereum in gwei terms, but it is calibrated so that a plain transfer (21,000 gas) costs about **0.1 NGRX**.
* Always read the price from the network (`eth_gasPrice` / `eth_feeHistory`) rather than hard-coding a value.
* Block gas limit is 75,000,000.

## Finality

Blocks are produced every 6 seconds and finalized by GRANDPA, normally two blocks behind the head. There are no probabilistic reorgs past finality, so indexers and bridges can wait for the `finalized` tag instead of a fixed number of confirmations.

## Accounts

Nagara uses Ethereum-style 20-byte addresses and secp256k1 keys natively, so the same address works for both EVM transactions and the chain's native token balance.


---

# 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.nagara.network/differences-from-ethereum.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.