Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
93 commits
Select commit Hold shift + click to select a range
600bb48
docs: The node config registry now declares the tendermint consensus …
seidroid[bot] Nov 18, 2026
fc6de5e
docs: The seid init command's generated node config file now declares…
seidroid[bot] Nov 18, 2026
0ab5f88
docs: The Giga SS Store default data-directory layout changed to back…
seidroid[bot] Nov 18, 2026
4bd4559
docs: The release build now produces a statically-linked seid binary …
seidroid[bot] Nov 18, 2026
428d4ee
docs: A new BEP-520-compatible `milliTimestamp` field (Unix milliseco…
seidroid[bot] Nov 18, 2026
4f619ca
docs: Adds capping of `/store/*/subspace` ABCI queries with new `[sta…
seidroid[bot] Nov 18, 2026
d91f4ec
docs: The default `telemetry.prometheus-retention-time` in app.toml d…
seidroid[bot] Nov 18, 2026
1eac585
docs: A new `receipt-store.rs-enable` config field lets node operator…
seidroid[bot] Nov 18, 2026
9768a75
docs: Adds two new EVM RPC config fields (max_filters, max_block_filt…
seidroid[bot] Nov 18, 2026
535c280
docs: The wasmd precompile's execute_batch method has been disabled a…
seidroid[bot] Nov 18, 2026
ae824d8
docs: The seidb evm_logical_digest WAL-replay path now opens memiavl …
seidroid[bot] Nov 18, 2026
c7a228c
docs: Adds a new `seid config check` subcommand that validates a node…
seidroid[bot] Nov 18, 2026
204a6ff
docs: Adds a receipt-store backend ownership marker file that refuses…
seidroid[bot] Nov 18, 2026
39c30b7
docs: The tmRPC /validators endpoint under Autobahn now returns the a…
seidroid[bot] Nov 18, 2026
75a0a0a
docs: Introduces an incremental/bounded governance tally system (gate…
seidroid[bot] Nov 18, 2026
13d8b58
docs: Go toolchain upgraded to 1.27.1 and the multistore state-sync s…
seidroid[bot] Nov 18, 2026
c313a17
docs: The mempool `max-tx-bytes` config field is now effectively unus…
seidroid[bot] Nov 18, 2026
d94953b
docs: Blob transaction validation now enforces EIP-4844 limits: a max…
seidroid[bot] Nov 18, 2026
84f861f
docs: Adds a pluggable LtHash hashing backend with an optional AVX-51…
seidroid[bot] Nov 18, 2026
813c09a
docs: The Giga EVM-only executor now emits OCC (optimistic concurrenc…
seidroid[bot] Nov 18, 2026
5760f04
docs: The EVM-only app's transaction admission now checks effective g…
seidroid[bot] Nov 18, 2026
4a0287b
docs: Adds a new BatchUpdate method and BatchUpdater interface to the…
seidroid[bot] Nov 18, 2026
50ebf77
docs: Adds a SIMD (AVX-512) batched SHA-256 backend for tmhash/merkle…
seidroid[bot] Nov 18, 2026
1668f0e
docs: The CLI command `seid tx evm register-cw-pointer` and the `MsgR…
seidroid[bot] Nov 18, 2026
45d96d1
docs: The seidb `evm-logical-digest` command gains a `--json` flag fo…
seidroid[bot] Nov 18, 2026
a44b3af
docs: EVM pointer contracts and their CLI commands/governance proposa…
seidroid[bot] Nov 18, 2026
87995b2
docs: Autobahn now requires on-disk persistent storage: the --persist…
seidroid[bot] Nov 18, 2026
e6ae949
docs: CHANGELOG references a new JSON output option for the seidb evm…
seidroid[bot] Nov 18, 2026
fa60ee4
docs: Adds a new Autobahn config field `max_concurrent_check_tx` to c…
seidroid[bot] Nov 18, 2026
e8a3604
docs: The `seid tx evm deploy-wsei` CLI command and its WSEI contract…
seidroid[bot] Nov 18, 2026
6c43ae2
docs: Adds a new EVM RPC metric `evmrpc_websocket_connections` tracki…
seidroid[bot] Nov 18, 2026
5a6db82
docs: The receipt-store config now rejects the 'littidx' backend in a…
seidroid[bot] Nov 19, 2026
61d9b10
docs: Adds eth_feeHistory and eth_gasPrice JSON-RPC methods to the gi…
seidroid[bot] Nov 19, 2026
57c2f00
docs: The Tendermint `evm-only` config field and `AUTOBAHN_EVMONLY` e…
seidroid[bot] Nov 19, 2026
28ff093
docs: Adds a new eth_estimateGas JSON-RPC method to the EVM-only RPC …
seidroid[bot] Nov 19, 2026
9bf89f1
docs: Adds the v6.8 chain upgrade with new versioned precompiles (add…
seidroid[bot] Nov 19, 2026
959f074
docs: Dynamic-gas precompiles that exhaust their Cosmos gas meter mid…
seidroid[bot] Nov 19, 2026
362251d
docs: This CHANGELOG update introduces numerous developer-facing chan…
seidroid[bot] Nov 19, 2026
b56ca72
docs: Adds a new `giga.storage.receipts` config field that controls w…
seidroid[bot] Nov 19, 2026
977169d
docs: FlatKV's default snapshot-keep-recent changed from 1 to 10 and …
seidroid[bot] Nov 19, 2026
1d76ff4
docs: The evmonly-loadtest tool gains new CLI flags (--accounts, --gc…
seidroid[bot] Nov 19, 2026
0bbb475
docs: Adds a configurable EVM-only JSON-RPC port via the new giga.exe…
seidroid[bot] Nov 19, 2026
2d73664
docs: Adds new Prometheus metrics for the autobahn consensus, availab…
seidroid[bot] Nov 19, 2026
3da3f17
docs: Adds a new EVM-only JSON-RPC WebSocket listener with a configur…
seidroid[bot] Nov 19, 2026
32247ec
docs: Adds per-method deadline enforcement for EVM JSON-RPC over HTTP…
seidroid[bot] Nov 19, 2026
e725cdd
docs: The v6.8 upgrade deletes the ibc, transfer, and capability stor…
seidroid[bot] Nov 19, 2026
3aba397
docs: Adds a 'pause-state-migration' hard fork handler that sets the …
seidroid[bot] Nov 19, 2026
b957f99
docs: Adds a new `seidb kvrepair-export` CLI command and a kvrepair h…
seidroid[bot] Nov 19, 2026
66e81de
docs: The seidb evm-logical-digest tool gains a new 'changelog' value…
seidroid[bot] Nov 19, 2026
4d27795
docs: EVM RPC block, filter, and log endpoints now return a clear err…
seidroid[bot] Nov 19, 2026
798c6fc
docs: Adds a new 'undolog' state store backend (PebbleDB-based undo l…
seidroid[bot] Nov 19, 2026
971dc3b
docs: The Autobahn view timeout moved from the autobahn.json file con…
seidroid[bot] Nov 19, 2026
5ffb9f8
docs: Rate limiting is now enabled by default across EVM RPC, gRPC, a…
seidroid[bot] Nov 19, 2026
7739972
docs: FlatKV rollback and historical reads now refuse versions outsid…
seidroid[bot] Nov 19, 2026
40973cd
docs: The ValidatorSlashes distribution query now filters by actual b…
seidroid[bot] Nov 19, 2026
4e33834
docs: Introduces configurable EVM RPC per-IP rate limiting via app.to…
seidroid[bot] Nov 19, 2026
579c50d
docs: Adds a new Prometheus metric `tendermint_p2p_known_addresses` g…
seidroid[bot] Nov 19, 2026
947ce25
docs: The staking precompile's redelegations query now enforces suppo…
seidroid[bot] Nov 19, 2026
7d3bba3
docs: The littidx receipt store backend was split into a new 'gigarec…
seidroid[bot] Nov 19, 2026
11afc06
docs: The bank precompile's spendableBalances now works for unassocia…
seidroid[bot] Nov 19, 2026
439b068
docs: Adds a new giga storage config field `state_store_backend` (and…
seidroid[bot] Nov 19, 2026
86670c0
docs: The tokenfactory module is removed behind the v6.8 upgrade, del…
seidroid[bot] Nov 19, 2026
cc64991
docs: The v6.8 upgrade introduces a new delegation-by-validator index…
seidroid[bot] Nov 19, 2026
6403ee0
docs: After the v6.8 tokenfactory removal, the Wasm `burn_tokens` cus…
seidroid[bot] Nov 19, 2026
d25dfc3
docs: The eth_sendRawTransaction JSON-RPC endpoint now maps Sei mempo…
seidroid[bot] Nov 20, 2026
d060884
docs: The EVM-only JSON-RPC now supports historical state queries: et…
seidroid[bot] Nov 20, 2026
f95f8f6
docs: The giga app hash subsystem gained a new on-disk app hash vault…
seidroid[bot] Nov 20, 2026
79206cd
docs: The v6.8 upgrade deletes the retired feegrant store, so from th…
seidroid[bot] Nov 20, 2026
39f826f
docs: The Docker image now builds and ships the seidb tool binary alo…
seidroid[bot] Nov 20, 2026
5946999
docs: Adds two governance-settable wasm params, msg_execute_contract_…
seidroid[bot] Nov 20, 2026
ed5bb1a
docs: The sc-subspace-query-max-inflight config field now bounds conc…
seidroid[bot] Nov 20, 2026
c810077
docs: Nodes with the state store (SS) disabled now reject all /subspa…
seidroid[bot] Nov 20, 2026
1552e49
docs: ABCI /store state proofs are disabled by default in v6.8; nodes…
seidroid[bot] Nov 20, 2026
ed5c2f6
docs: eth_getFilterLogs is now a read-only history query that no long…
seidroid[bot] Nov 20, 2026
c2334b4
docs: EVM transactions no longer include return data and logs in the …
seidroid[bot] Nov 20, 2026
683aa99
docs: Adds a new `paritycapture` developer command-line tool for reco…
seidroid[bot] Nov 20, 2026
a8cf1db
docs: The Cosmos gRPC and gRPC-Web servers (and the Rosetta API serve…
seidroid[bot] Nov 20, 2026
4cf5387
docs: The behavior of eth_newFilter, eth_getFilterChanges, eth_getFil…
seidroid[bot] Nov 20, 2026
8398bf1
docs: Rosetta API support has been fully removed from Sei — the Roset…
seidroid[bot] Nov 20, 2026
95414aa
docs: The experimental v2 config manager (SEI_CONFIG_MANAGER=v2 env v…
seidroid[bot] Nov 20, 2026
8453284
docs: The Autobahn/giga validator EVM RPC URL now requires a WebSocke…
seidroid[bot] Nov 20, 2026
2b0bc1b
docs: EVM RPC methods that take a block identifier or range now retur…
seidroid[bot] Nov 20, 2026
4a38b92
docs: EVM log filters (eth_newFilter, eth_getFilterChanges, eth_subsc…
seidroid[bot] Nov 20, 2026
c9f91ec
docs: The v6.8 upgrade handler now halts the node if retired stores w…
seidroid[bot] Nov 20, 2026
0881712
docs: Rate-limited JSON-RPC batch POST requests now return an HTTP 42…
seidroid[bot] Nov 20, 2026
c246bd1
docs: Adds a new `audit-flatkv` subcommand to the seidb tool that ver…
seidroid[bot] Nov 20, 2026
85b70c9
docs: The behavior of eth_newBlockFilter and the max_block_filter_has…
seidroid[bot] Nov 20, 2026
f5118f5
docs: The statesync.trust-period config field was removed; state sync…
seidroid[bot] Nov 20, 2026
069bf3b
docs: eth_getLogs, eth_getFilterLogs, and eth_getFilterChanges log po…
seidroid[bot] Nov 20, 2026
74b6e2f
docs: FinalizeBlock responses larger than 1 GiB are now stored withou…
seidroid[bot] Nov 20, 2026
75948b0
docs: Governance deposit burning/refunding for finished proposals is …
seidroid[bot] Nov 20, 2026
cba09bf
docs: When incremental tally is enabled, gov deposits are now validat…
seidroid[bot] Nov 20, 2026
18368b1
docs: A new configurable node-wide rate limit for large log queries (…
seidroid[bot] Nov 20, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion cosmos-sdk/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,10 @@ Cosmos SDK and CosmWasm functionality is being deprecated in favor of EVM-only.

In addition, [Proposal 115](https://seistream.app/proposals/115) disables CosmWasm code uploads (`MsgStoreCode`) and contract instantiations (`MsgInstantiateContract`) chain-wide. No new CosmWasm contracts can be deployed. Only `execute` and `query` against pre-existing contracts remain available through the [CosmWasm precompile](/evm/precompiles/cosmwasm-precompiles/cosmwasm).



As of the v6.8 upgrade (#4564), governance can halt CosmWasm contract execution in stages through two new wasm module params, each settable with a param-change proposal against the `wasm` subspace. While `msgExecuteContractDisabled` is `true`, every `MsgExecuteContract` fails (codespace `wasm`, code 31), whether sent directly, wrapped in an authz `MsgExec`, or dispatched by a contract; the EVM wasmd precompile, solo claims, and wasm gov proposals still execute. While `contractExecutionDisabled` is `true`, no contract runs at all (codespace `wasm`, code 32): every instantiation, execution, migration, and sudo call fails whatever its origin, including the EVM wasmd and solo precompiles and wasm gov proposals, so even `execute` against pre-existing contracts stops working; `query` still works. Both params default to `false` and are stored as `false` at the upgrade (the wasm module moves to consensus version 2, app-hash breaking at the upgrade height).

**IBC is now disabled in both directions.** [Proposal 116](https://seistream.app/proposals/116) and [Proposal 120](https://seistream.app/proposals/120) set the `ibc` module's `InboundEnabled` parameter to `false`, and [Proposal 121](https://seistream.app/proposals/121) set `OutboundEnabled` to `false` on July 31, 2026. No asset can be bridged into or out of Sei over IBC. IBC assets already on Sei can no longer be redeemed on their origin chain. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for the full explanation and the list of affected assets.

</Danger>
Expand All @@ -22,6 +26,8 @@ In addition, [Proposal 115](https://seistream.app/proposals/115) disables CosmWa

<Warning>

Tokenfactory tutorials and development support have been retired as part of Sei's move to EVM-only under SIP-3. Do not create, mint, burn, administer, or build integrations around tokenfactory denoms. Legacy module and RPC surfaces may still exist for compatibility, but tokenfactory is not a supported path for new development. Deploy an ERC-20 contract instead.
The tokenfactory module is removed as of the v6.8 upgrade. The module, its store, params, CLI commands (`seid tx tokenfactory ...` and `seid q tokenfactory ...`), gRPC/REST query and Msg services, and nearly all CosmWasm bindings are gone. Do not create, mint, administer, or build new integrations around tokenfactory denoms. Only the tokenfactory Msg types remain decodable so historical blocks still trace; any such message now fails validation (codespace `tokenfactory`, code 26, "tokenfactory module is deprecated") and is rejected without charging a fee. Existing `factory/` balances remain in the bank module and can no longer be minted, and denoms that previously carried a transfer allowlist now transfer freely, since the bank `factory/` denom transfer allowlist enforcement has been removed.

One exception survives the removal (#4549): the `burn_tokens` Wasm custom message still works, so a contract can burn a `factory/<contract>/<subdenom>` denom it created, from its own balance. The handler accepts only denoms the calling contract created (prefix `factory/<contract>/`) and burns from that contract's own balance; `mint_tokens` and every other tokenfactory Wasm message remain removed and unsupported. For new tokens, deploy an ERC-20 contract instead.

</Warning>
19 changes: 19 additions & 0 deletions evm/changelog.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,25 @@ Stay up to date with the latest changes, improvements, and new features in Sei.

<Info>This changelog is automatically synced from the [sei-chain repository](https://github.com/sei-protocol/sei-chain/blob/main/CHANGELOG.md). For the most up-to-date information, you can also view the changelog directly on GitHub.</Info>

<Note>

**v6.8 chain upgrade**

The v6.8 chain upgrade introduces new versioned EVM precompiles that expose additional on-chain query and authorization methods to contract developers. Node operators must upgrade to the v6.8 binary before the scheduled plan height; an unupgraded binary halts at that height.

Newly exposed precompile methods include:

- **Auth** (`0x…100D`): `account`, `accounts`, `params`, `nextAccountNumber`.
- **Authz** (`0x…100E`): `grants`, `granterGrants`, `granteeGrants`.
- **Evidence** (`0x…100F`): `evidence`, `allEvidence`.
- **Bank** (`0x…1001`): adds `spendableBalances`, `totalSupply`, `params`, `denomMetadata`, `denomsMetadata` alongside the existing send/balance methods.
- **Distribution** (`0x…1007`): adds `communityPool`, `params`, `validatorOutstandingRewards`, `validatorCommission`, `validatorSlashes`, `delegationRewards`, `delegatorValidators`, `delegatorWithdrawAddress`, `grantWithdrawAuthorization`, `revokeWithdrawAuthorization`, `withdrawDelegationRewardsWithAuthorization`, `withdrawValidatorCommissionWithAuthorization`.
- **Gov** (`0x…1006`): adds `proposal`, `proposals`, `getVote`, `votes`, `params`, `getDeposit`, `deposits`, `tallyResult`, `grantVoteAuthorization`, `grantProposalAuthorization`, `voteWithAuthorization`, `submitProposalWithAuthorization`, `revokeVoteAuthorization`, `revokeProposalAuthorization`, `voteWeighted`.

The upgrade also adds two governance-settable wasm params that halt CosmWasm contract execution in stages (#4564). While `msg_execute_contract_disabled` is `true`, every `MsgExecuteContract` fails, whether sent directly, wrapped in an authz `MsgExec`, or dispatched by a contract; the EVM wasmd precompile, solo claims, and wasm gov proposals still execute. While `contract_execution_disabled` is `true`, no contract runs: every instantiation, execution, migration, and sudo call fails from any origin, including the EVM wasmd and solo precompiles and wasm gov proposals, while queries still work. Both params default to `false` and are settable via a param-change governance proposal under the `wasm` subspace (keys `msgExecuteContractDisabled` and `contractExecutionDisabled`). The wasm module moves to consensus version 2 and stores both params as `false` at the upgrade, which is app-hash breaking at the upgrade height.

</Note>

<Info>

**Stay updated**
Expand Down
7 changes: 4 additions & 3 deletions evm/evm-parity/evm-compatibility.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,8 @@ Standard EVM tools (viem, wagmi, ethers, Foundry, and Hardhat) work on Sei for a

| Feature | Sei status | Notes |
| --- | --- | --- |
| `eth_getLogs` | Supported with differences | A query fails when it matches more than 10,000 logs (`max_log_no_block`) or about 64 MiB of log data (`max_log_bytes`). The query does not return partial results. Narrow the block range or the filters, then try again. [See Filter and subscription limits.](/evm/reference#filter-and-subscription-limits) |
| Filter lifecycle (`eth_newFilter`, `eth_getFilterChanges`, `eth_getFilterLogs`, `eth_uninstallFilter`) | Supported | |
| `eth_getLogs` | Supported with differences | A query fails when it matches more than 10,000 logs (`max_log_no_block`) or about 64 MiB of log data (`max_log_bytes`). The query does not return partial results. Narrow the block range or the filters, then try again. On a state-synced or snapshot-restored node the receipt store can start later than the block store; the earliest queryable height is this receipt floor. A block-range or block-hash query targeting a height below the floor returns JSON-RPC error `-32000` (receipts pruned) instead of empty results, while an unknown block hash still returns no blocks. `eth_getLogs`, `eth_getFilterLogs`, and each `eth_getFilterChanges` poll share one admission check before reading: a range over `max_blocks_for_log` is refused, and a range over 100 blocks consumes a token from a large-query rate limiter shared by all three. A refusal for rate limiting or server load returns JSON-RPC error `-32005` (limit exceeded, retry later) and carries no internal server counts; retry after a short delay. [See Filter and subscription limits.](/evm/reference#filter-and-subscription-limits) |
| Filter lifecycle (`eth_newFilter`, `eth_getFilterChanges`, `eth_getFilterLogs`, `eth_uninstallFilter`) | Supported with differences | `eth_getFilterLogs` and each `eth_getFilterChanges` poll pass the same admission as `eth_getLogs` (see above), sharing one large-query rate-limit budget. Without a token, `eth_getFilterLogs` is refused with `-32005` while a filter poll is cut to the next 100 blocks so it keeps advancing. A poll refused for server load leaves the cursor in place and returns `-32005`. |
| WebSocket subscriptions (`eth_subscribe`) | Supported | [See WebSocket Connections.](/evm/evm-parity/websocket) |

## Execution and simulation
Expand Down Expand Up @@ -101,8 +101,9 @@ These features are specific to Sei and have no standard Ethereum equivalent. The
| Feature | Notes |
| --- | --- |
| Sei precompiles (staking, governance, distribution, P256, JSON, Solo, pointers, and the CosmWasm bridge) | EVM contracts at deterministic addresses. `@sei-js/precompiles` exports the ABIs and contract addresses for use with any standard EVM library. It does not export the retired Oracle and disabled IBC precompiles. |
| Pointer contracts (CW20 ↔ ERC-20, CW721 ↔ ERC-721, CW1155 ↔ ERC-1155) | Bridge between CosmWasm and EVM token standards. Standard ERC interfaces work with pointer contracts. To look up a pointer, use `POINTERVIEW_PRECOMPILE_ADDRESS` (`0x…100A`). To register a pointer, use `POINTER_PRECOMPILE_ADDRESS` (`0x…100B`). |
| Pointer contracts (CW20 ↔ ERC-20, CW721 ↔ ERC-721, CW1155 ↔ ERC-1155) | Bridge between CosmWasm and EVM token standards. Standard ERC interfaces work with pointers that already exist. Pointer creation is retired: the pointer precompile at `POINTER_PRECOMPILE_ADDRESS` (`0x…100B`) stays registered but every `add*` call reverts with `pointer precompile is retired; EVM pointer creation is disabled`, so no new pointer of any kind can be created. Only lookups remain available — use `POINTERVIEW_PRECOMPILE_ADDRESS` (`0x…100A`) to resolve an existing pointer. |
| Native address association (EVM ↔ Cosmos address) | Links an EVM address and a Cosmos address for the same account. Some Sei-native flows require this association first. |
| `milliTimestamp` block-header field | A BEP-520-compatible header field returned by `eth_getBlockByHash`, `eth_getBlockByNumber`, and `eth_subscribe("newHeads")`, carrying the block time as a hex quantity of Unix milliseconds alongside the standard seconds-based `timestamp`. Sei commits blocks faster than once a second, so `timestamp` repeats across consecutive blocks; `milliTimestamp` exposes the sub-second precision the underlying header carries. It is not guaranteed unique per block (under Autobahn blocks less than a millisecond apart can tie). The synthetic genesis block returns `0x0`. |

## Unsupported RPC methods

Expand Down
57 changes: 57 additions & 0 deletions evm/evm-parity/examples/error-handling.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -153,6 +153,63 @@ try {

## Classifying any error



## Broadcast rejections

When you submit a signed transaction with `eth_sendRawTransaction`, Sei's mempool may reject it before it is ever included in a block. These rejections are now mapped to the same standard go-ethereum error types that EVM clients already recognize, so you can handle them with the same logic you use against other Ethereum networks:

| Condition | Returned error |
| --- | --- |
| Transaction is already pending in the mempool | `ErrAlreadyKnown` (`already known`) |
| Transaction nonce is below the sender's lowest pending nonce | `ErrNonceTooLow` (`nonce too low`) |
| A transaction with the same nonce and at least the same priority is already held | `ErrReplaceUnderpriced` (`replacement transaction underpriced`) |
| The transaction would replace a ready transaction but the sender can't afford it | `ErrInsufficientFunds` (`insufficient funds for gas * price + value`) |

Because these are the canonical Ethereum broadcast errors, you can match on their messages (or the equivalent error classes your client exposes):

<CodeGroup>

```ts viem
try {
await walletClient.sendRawTransaction({ serializedTransaction });
} catch (err) {
const message = (err as Error).message ?? '';
if (message.includes('already known')) {
// Transaction is already in the mempool — treat as a duplicate submit, don't resend
console.log('Transaction already known');
} else if (message.includes('nonce too low')) {
// Nonce was already used — refetch the pending nonce and rebuild
console.error('Nonce too low');
} else if (message.includes('replacement transaction underpriced')) {
// Bump the gas price/priority fee to replace the pending tx
console.error('Replacement underpriced');
} else if (message.includes('insufficient funds')) {
console.error('Insufficient funds for this transaction');
}
}
```

```ts ethers
try {
await provider.broadcastTransaction(signedTx);
} catch (err: any) {
const message = err?.error?.message ?? err?.message ?? '';
if (message.includes('already known')) {
console.log('Transaction already known');
} else if (err.code === 'NONCE_EXPIRED' || message.includes('nonce too low')) {
console.error('Nonce too low');
} else if (err.code === 'REPLACEMENT_UNDERPRICED' || message.includes('replacement transaction underpriced')) {
console.error('Replacement underpriced');
} else if (err.code === 'INSUFFICIENT_FUNDS' || message.includes('insufficient funds')) {
console.error('Insufficient funds for this transaction');
}
}
```

</CodeGroup>


This utility handles the most common cases in one place:

```ts
Expand Down
4 changes: 4 additions & 0 deletions evm/evm-parity/examples/pointer-contracts.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,10 @@ After you have the pointer address, you interact with it through the standard ER

For background on how pointer contracts work, see the [Pointers overview](/learn/pointers).

<Note>
This page covers CosmWasm→EVM pointers (a CW20/CW721/CW1155 token exposed through an ERC-20/721/1155 pointer). The reverse direction — wrapping an ERC20/721/1155 token in a CosmWasm CW20/CW721/CW1155 wrapper via `MsgRegisterPointer` — has been retired. That handler now returns `ErrRegisterPointerDeprecated` and the wrapper bytecode is no longer shipped, so no new CW wrappers for ERC tokens can be created. Wrappers registered before the retirement remain live and readable: their registry entries, versions, and queries are unchanged, and `AssociateContractAddress` still gives such a wrapper an EVM address.
</Note>

## Looking up a pointer address

The pointerview precompile resolves pointer addresses for existing CosmWasm contracts. `@sei-js/precompiles` exports its ABI and address.
Expand Down
2 changes: 2 additions & 0 deletions evm/evm-parity/finality.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,8 @@ On Ethereum, `latest`, `safe`, and `finalized` refer to different points in the

On Sei, all three tags resolve to the same block. After a block is committed, there is no reorg risk at any point, so the distinction does not exist.

Under the EVM-only RPC, state-reading methods differ in how they treat an explicit past block. `eth_getBalance`, `eth_getTransactionCount`, `eth_getCode`, and `eth_getStorageAt` accept an explicit block height (or `earliest`, which reads block 0) in addition to the latest-equivalent tags (`latest`, `safe`, `finalized`, `pending`). A past height is served from the EVM state store, so it requires a node that keeps state history (a full node, not a validator) and fails once that height is pruned. A block hash, or a height above the current head, returns an error. `eth_call` still accepts only the latest-equivalent tags; an explicit height, a block hash, or `earliest` returns an error, because calls do not run against historical state.

<CodeGroup>

```ts viem
Expand Down
12 changes: 12 additions & 0 deletions evm/evm-parity/gas-and-fees.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,17 @@
In practice, when your priority tip plus the base fee stays below `maxFeePerGas`, the receipt reports `baseFee + maxPriorityFeePerGas`, not `maxFeePerGas`. To compute what a transaction paid, use the receipt's `effectiveGasPrice`, not `maxFeePerGas`.



### Admission is priced on effective gas price

Transaction admission at `CheckTx` compares a transaction's **effective gas price** against the minimum gas price, not its fee cap. For a dynamic-fee (type 2) transaction the effective gas price is `min(baseFee + maxPriorityFeePerGas, maxFeePerGas)`, which at a zero base fee reduces to `maxPriorityFeePerGas` (the tip).

As a result, a dynamic-fee transaction with a high `maxFeePerGas` but a low or zero `maxPriorityFeePerGas` is rejected at admission, even though its fee cap would clear the floor. Admission is priced on the same quantity block validity uses, so a transaction that was admitted on its fee cap alone would later be refused by the executor.

When setting fees for a dynamic-fee transaction, make sure `maxPriorityFeePerGas` alone (not just `maxFeePerGas`) meets the minimum gas price. A transaction that fails this check is rejected with an `effective gas price is below` error.


## SSTORE cost

Check warning on line 74 in evm/evm-parity/gas-and-fees.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

evm/evm-parity/gas-and-fees.mdx#L74

Use sentence case for headings: 'SSTORE cost'.

On Sei, governance can adjust the gas cost of `SSTORE` (a write to contract storage). The current cost is **72,000 gas** on both Sei Mainnet and Sei Testnet. For details, see [Differences with Ethereum](/evm/differences-with-ethereum#sstore-gas-cost). Treat this number as the current value, not a constant. Do not hard-code storage write estimates in your application.

Expand Down Expand Up @@ -101,6 +111,8 @@
- The pointer view precompile also charges for the state that each lookup reads.
- The P256 precompile also charges a fixed 3,450 gas per verification, the same as RIP-7212 `P256VERIFY`. If the call cannot pay it, the call fails with an out-of-gas error.

When a dynamic-gas precompile (such as JSON, P256, or pointer view) runs out of gas partway through execution, the out-of-gas condition fails as a standard EVM out-of-gas call (#4318): it fails only that EVM call frame rather than the whole transaction. The frame's gas is fully consumed, any state changes it made are reverted, and the enclosing frame is free to continue. The transaction completes as a normal failed EVM execution: it produces a failed EVM receipt carrying the real gas used and effective gas price, and the sender is charged for exactly the gas consumed.

Because the cost depends on your calldata, do not hard-code gas limits for precompile calls. Use `eth_estimateGas`, as shown in the example above.

## Summary
Expand Down
12 changes: 12 additions & 0 deletions evm/evm-parity/transaction-types.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,18 @@ Sei runs the Pectra hardfork without blob transaction support. If you try to sen

If you port code from Ethereum that uses blob transactions (for example, for rollup data availability), that code path does not apply to Sei.


### Blob transaction validation limits

Beyond RPC-level rejection, blob (EIP-4844) transaction validation enforces EIP-4844 structural limits. A blob transaction is rejected during validation if any of the following hold:

- It carries more than 6 blob hashes, or a sidecar with more than 6 blobs, commitments, or proofs.
- The sidecar's blob, commitment, and proof counts do not all match each other.
- The number of blob hashes does not match the number of sidecar blobs.
- Any sidecar blob, commitment, or proof does not have the exact fixed KZG byte length.

If you construct blob-shaped transactions, these checks reject malformed or oversized blob transactions before they can be processed.

## Sending transactions

Standard library defaults work correctly. viem, wagmi, and ethers all default to type 2 (EIP-1559) transactions on chains that support EIP-1559, and Sei does.
Expand Down
Loading
Loading