WIP Evm docs updates by evanorti · Pull Request #210 · cosmos/docs

evanorti · 2026-02-17T22:10:59Z

Update EVM docs files and streamline

Add a single comprehensive EVM compatibility guide (evm/next/documentation/evm-compatibility.mdx) that documents supported EIPs/ERCs/opcodes, tooling, precompiles, JSON‑RPC behavior, and Cosmos-specific capabilities (finality, fees, addresses, chain IDs, performance). Remove now-redundant subpages: eip-2935.mdx, eip-7702.mdx, eip-reference.mdx, and overview.mdx to centralize compatibility information and avoid duplication.

vladjdk · 2026-02-24T00:46:01Z

evm/next/documentation/concepts/mempool.mdx


+### Transaction Type Routing
+
+**Ethereum transactions (`MsgEthereumTx`)**: Routed to the EVM TxPool, which handles nonce gaps, promotion, and eviction. Executable transactions are then broadcast via CometBFT P2P.


This will definitely change after Krakatoa

I was told that the mempool stays as-is, and krakatoa is an opt-in feature, so we'll put krakatoa docs in an "experimental features" section.

vladjdk · 2026-02-24T00:47:43Z

...documentation/getting-started/build-a-chain/additional-configuration/mempool-integration.mdx

+The mempool setup is split across two locations:

-### Step 1: Add EVM Mempool to App Struct
+- [`evmd/mempool.go`](https://github.com/cosmos/evm/blob/main/evmd/mempool.go) — `configureEVMMempool` and `createMempoolConfig`, called automatically from `NewExampleApp`


What does "automatically" mean?

This is something we need to include to app.go

Updated to:

- [`evmd/mempool.go`](https://github.com/cosmos/evm/blob/main/evmd/mempool.go) — `configureEVMMempool` and `createMempoolConfig`, which must be called from your `app.go` after `setAnteHandler`

wdyt?

...documentation/getting-started/build-a-chain/additional-configuration/mempool-integration.mdx

vladjdk · 2026-02-24T01:04:50Z

evm/next/documentation/getting-started/build-a-chain/additional-configuration/precompiles.mdx

+
+## Enabling Precompiles
+
+Precompiles are enabled via the `active_static_precompiles` parameter in the `vm` module. Only addresses listed here are callable at runtime. For the full list of built-in precompiles and their addresses, see the [precompiles overview](/evm/next/documentation/smart-contracts/precompiles/overview).


You also need to wire them in during the app.go wiring (either with DefaultPrecompiles) or with your own set.

done. please review the file changes

vladjdk · 2026-02-24T01:06:07Z

evm/next/documentation/getting-started/build-a-chain/additional-configuration/precompiles.mdx

+}
+```
+
+To enable only a specific subset, pass the addresses explicitly. Addresses must be in sorted order:


Addresses must be in sorted order:

I'm actually not sure this is true - what tells you this?

"Sorted order is required for determinism. This is enforced by ValidatePrecompiles in x/vm/types/params.go — validation fails with "precompiles need to be sorted" if slices.IsSorted(precompiles) returns false.
"

@vladjdk I think it's enforced

evm/next/documentation/evm-compatibility.mdx

evm/next/documentation/getting-started/faq.mdx

vladjdk · 2026-02-24T01:46:42Z

evm/next/documentation/smart-contracts/precompiles/overview.mdx

 ---

-## Available Precompiles
+Precompiles are smart contract interfaces deployed at fixed addresses where the implementation runs as native Go code rather than EVM bytecode. In standard Ethereum, precompiles are stateless and handle things like signature verification and hashing. In Cosmos EVM, they can also be stateful — reading from and writing to Cosmos SDK module state outside the EVM.


I feel like we may have repeated this 3 times

Yeah, but in different places like the faq so I think it's ok.

vladjdk · 2026-02-24T01:47:16Z

evm/next/documentation/smart-contracts/precompiles/overview.mdx

+This is what makes them powerful: a smart contract can call the staking precompile to delegate tokens, the governance precompile to submit a proposal, or the IBC precompile to send tokens cross-chain — all using a standard Solidity interface, all within a single transaction.

-Precompiled contracts provide direct, gas-efficient access to native Cosmos SDK functionality from within the EVM. Build powerful hybrid applications that leverage the best of both worlds. This page provides an overview of the available precompiled contracts, each with detailed documentation on its usage, Solidity interface, and ABI.
+Calls are bidirectional. EVM contracts can call precompiles, and precompiles can call back into EVM contracts. When a precompile is invoked, execution routes from the EVM through the corresponding Cosmos SDK module and returns the result to the EVM for continued execution. Gas is metered across both environments.


I don't want to specify that they can call back into the EVM. Let's just say that it's a window into the Cosmos SDK space

"Precompiles act as a window into the Cosmos SDK: when a precompile is invoked, execution routes from the EVM through the corresponding Cosmos SDK module and returns the result to the EVM for continued execution. Gas is metered across both environments."

vladjdk · 2026-02-24T01:47:45Z

evm/next/documentation/smart-contracts/precompiles/overview.mdx

-  // WRONG: Assuming Ethereum's 18 decimals
-  uint256 amount = 1 ether; // 1000000000000000000
-  staking.delegate(validator, amount); // Delegates 1 trillion tokens!
+  Cosmos chains typically use 6 decimals. Passing a value like `1000000000000000000` (1 ETH in wei) to a precompile on a 6-decimal chain will be interpreted as 1 trillion tokens.


NO

Specify 18 decimals on Cosmos chains. There's no modern reason why you should use 6

@vladjdk

is this good?

<Warning> All precompile contracts should use Ethereum's standard 18 decimals. Although typical Cosmos chains use 6 decimals, EVM chains should use 18 decimals. Always check your chain's decimal precision before interacting with a precompile. </Warning>

evanorti added 4 commits February 17, 2026 17:10

Update docs.json

b7cc273

Update methods.mdx

ca93ea3

Update overview.mdx

9451122

evanorti marked this pull request as ready for review February 17, 2026 22:12

evanorti added 2 commits February 17, 2026 17:13

Update evm-compatibility.mdx

4fbfd82

Update evm-compatibility.mdx

44984df

mintlify bot deployed to staging February 17, 2026 22:14 View deployment

mintlify bot deployed to staging February 17, 2026 22:23 View deployment

evanorti added 4 commits February 18, 2026 16:12

Update mempool.mdx

9c5a7f0

Update mempool-integration.mdx

43a2380

Update predeployed-contracts.mdx

dae7ffb

Update quick-start.mdx

e12ec71

mintlify bot deployed to staging February 18, 2026 21:13 View deployment

evanorti added 5 commits February 18, 2026 18:07

Update docs.json

f8ed2f9

Delete predeployed-contracts.mdx

d37c46e

Update predeployed-contracts.mdx

392b649

Update overview.mdx

5a5ad27

remove unneeded pages

cf1bf78

mintlify bot deployed to staging February 18, 2026 23:09 View deployment

update tools page

8a36bc3

mintlify bot deployed to staging February 19, 2026 17:46 View deployment

evanorti added 8 commits February 19, 2026 14:51

Update evm-compatibility.mdx

f9efb45

Update overview.mdx

e84c194

Update introduction.mdx

69e950a

Create precompiles.mdx

fb24e24

Update quick-start.mdx

dd448c0

Update docs.json

4ee9439

Update evm-compatibility.mdx

fdca002

Update quick-start.mdx

596d408

mintlify bot deployed to staging February 19, 2026 20:25 View deployment

evanorti added 7 commits February 19, 2026 16:53

Update docs.json

c46edc4

Update erc20.mdx

4f811e8

Update evm-compatibility.mdx

b6aeea6

Update faq.mdx

5467cdf

Update overview.mdx

e07b3ad

Delete introduction.mdx

9f746a5

Delete index.mdx

eda99ba

mintlify bot deployed to staging February 19, 2026 21:57 View deployment

Update precompiles.mdx

422c416

mintlify bot deployed to staging February 19, 2026 22:16 View deployment

evanorti requested a review from vladjdk February 19, 2026 22:23

vladjdk requested changes Feb 24, 2026

View reviewed changes

Merge main into evm-docs-updates

2d170cf

mintlify bot deployed to staging February 24, 2026 15:36 View deployment

updates

3a74c2c

mintlify bot deployed to staging February 24, 2026 17:34 View deployment


		### Transaction Type Routing

		Ethereum transactions (`MsgEthereumTx`): Routed to the EVM TxPool, which handles nonce gaps, promotion, and eviction. Executable transactions are then broadcast via CometBFT P2P.


		## Enabling Precompiles

		Precompiles are enabled via the `active_static_precompiles` parameter in the `vm` module. Only addresses listed here are callable at runtime. For the full list of built-in precompiles and their addresses, see the [precompiles overview](/evm/next/documentation/smart-contracts/precompiles/overview).

Comments

Conversation

evanorti commented Feb 17, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

evanorti Feb 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

evanorti Feb 24, 2026 •

edited

Loading