Skip to content

Releases: sei-protocol/sei-chain

v6.4.3

29 Apr 22:46
5e40756

Choose a tag to compare

This is a non-mandatory release, but upgrading is strongly recommended as it includes a number of stability fixes, RPC correctness improvements, and consensus-related enhancements that benefit node operators, validators, and application developers building on Sei.

EVM JSON-RPC Correctness Improvements

This release ships two notable fixes to the EVM JSON-RPC layer that improve compatibility with Ethereum tooling and client libraries.

Batch request handling has been improved so that batches containing duplicate or null request IDs are now processed correctly on the slow path. Previously, duplicate or null IDs could cause responses to be misaligned with their corresponding requests; the fix introduces synthetic internal IDs to ensure each request in a batch is tracked and returned independently.

Additionally, eth_getFilterLogs and eth_getFilterChanges now return an empty array ([]) when there are no matching results, rather than returning null. This aligns Sei's behavior with the Ethereum JSON-RPC specification and resolves issues with web3 libraries that expect an iterable response.

Consensus WAL Lock Cleanup on Shutdown

A long-standing issue where the file lock (flock) on the consensus Write-Ahead Log was not released when a node shut down has been resolved. Operators who restarted nodes quickly, or whose process management tooling relied on lock state, occasionally encountered situations where a fresh node process could not acquire the WAL. The lock is now properly released as part of the shutdown sequence, making restarts cleaner and more reliable.

Proposer Priority Divergence Monitoring

Two related changes improve validator-set divergence detection. The ProposerPriorityHash is now exported as a metric, giving operators and the broader network a way to observe and alert on proposer-priority divergence between nodes — an early signal of state inconsistency.

The light client divergence detector has also been hardened to handle a previously unhandled error case, making divergence detection more robust in adverse network conditions.

Updated Cryptographic Dependencies

This release includes upstream updates to cryptographic library dependencies. Operators are encouraged to upgrade to stay current with maintained versions of these libraries.

What's Changed

  • backported crypto library fixes by @pompon0 in #3273
  • Backport release/v6.4: Fix buffer offset in ProposerPriorityHash (CON-200) by @Seidroid[bot] in #3283
  • new short term election algorithm by @pompon0 in #3270
  • Backport release/v6.4: Handle error case in light client divergence detector by @Seidroid[bot] in #3282
  • Backport release/v6.4: Export ProposerPriorityHash metric for divergence monitoring by @Seidroid[bot] in #3286
  • Backport release/v6.4: fix: flock to consensus WAL was not unlocked when shutting down the node by @Seidroid[bot] in #3315
  • Backport release/v6.4: fix(evmrpc): return empty array instead of null for eth_getFilterLogs and eth_getFilterChanges by @Seidroid[bot] in #3324
  • Backport release/v6.4: fix(evmrpc): use synthetic IDs in slow-path batch to handle duplicate and null request IDs by @Seidroid[bot] in #3333
  • Update Changelog in prep for release by @masih in #3342
  • Bump version to v6.4.3 in prep for tag cut by @masih in #3343

Full Changelog: v6.4.2...v6.4.3

v6.4.2

14 Apr 15:55
687fab0

Choose a tag to compare

Receipt Pruning Fix

This is an optional upgrade for mainnet, but highly recommended for all node operators. A bug introduced in v6.4.0 (via #3035) silently changed the receipt store's KeepRecent default from min-retain-blocks (typically 0 on archive nodes) to a hardcoded value of 100,000. This caused historical receipt data older than ~100k blocks (~13 hours) to be incorrectly pruned immediately upon upgrading to v6.4.0.

v6.4.2 fixes this by reverting the receipt retention default to honor min-retain-blocks, preventing further data loss.

Caveats and guidance for node operators:

  • RPC nodes: Upgrade to v6.4.2 to stop further pruning. If your node has more than 100k blocks of history and you need older receipts, you will need to state sync after upgrading.
  • Archive nodes: Upgrading to v6.4.2 will prevent additional receipt loss going forward, but it will not recover receipts that were already pruned. To restore full historical receipt data, you must restore from a pre-v6.4.0 snapshot and replay to the current height using v6.4.2. The Sei team is also preparing a restored archive node with complete receipt history — reach out if you need access to this.
  • Validators / non-archive nodes: The bug is still present on v6.4.1, but the practical impact is lower for nodes that are already pruning block data, since there is limited value in retaining receipts beyond your block retention window. Upgrading to v6.4.2 is still recommended to ensure network consistency.

What's Changed

  • Backport release/v6.4: added a ProposerAddress check to setProposal CON-250 by @Seidroid[bot] in #3233
  • Backport release/v6.4: Fix receipt default retention by @Seidroid[bot] in #3238
  • Backport release/v6.4: Regenerate changelog in prep to tag v6.4.2 by @Seidroid[bot] in #3241
  • Bump tag in prep to publish release v6.4.2 by @masih in #3242

Full Changelog: v6.4.1...v6.4.2

v6.4.1

08 Apr 20:54
fb91ad3

Choose a tag to compare

Mandatory Mainnet Chain Upgrade

What's Changed

  • Add v154 wasmvm library compatibility documentation by @masih in #3199
  • Backport release/v6.4: feat(mempool): only allow one retry for failed txs by @Seidroid[bot] in #3201
  • Backport release/v6.4: Unify EVM SS into single DB with store key prefixes by @Seidroid[bot] in #3211
  • Backport release/v6.4: Update Changelog in prep to cut v6.4.1 by @Seidroid[bot] in #3214
  • Bump version file to v6.4.1 in prep to cut tag by @masih in #3215

Full Changelog: v6.4.0...v6.4.1

v6.4.0

04 Apr 12:56
v6.4.0
8cbbadf

Choose a tag to compare

What's Changed

Read more

v6.3.3

24 Feb 16:22
2e97475

Choose a tag to compare

  • Add metrics for historical proof success/failure rate
  • Reduce SS changelog retention to use the async buffer size
  • Add Rate limit and concurrency control for RPC with proof queries
  • fix: pruning goroutine lifecycle and prune failure snapshot
  • Check existing memiavl config before setting default
  • bugfix: make router load addresses from peerdb
  • fixed autorestart cooldown

v6.3.2

14 Feb 02:59
cf86df0

Choose a tag to compare

Includes fixes for:

  • Using ledger to sign / broadcast txs
  • Various storage performance improvements (rate limiting to prevent high io usage)
  • P2P fixes

v6.3.1

28 Jan 17:30
c68f987

Choose a tag to compare

See CHANGELOG here: https://github.com/sei-protocol/sei-chain/blob/main/CHANGELOG.md
pacific-1 Estimated upgrade time: 2026-02-03T16:00:00
Upgrade height: 192196147
Proposal: https://www.mintscan.io/sei/proposals/108

v6.3.0

23 Jan 19:42
6d761d9

Choose a tag to compare

v6.3.0 Pre-release
Pre-release
Backport `release/v6.3`: Update `cosmwasm` to reftype fix via forked …

v6.2.6

16 Dec 02:29
fc7cf5f

Choose a tag to compare

Adds eth_getLogs performance with early rejection and backpressure

v6.2.5

21 Nov 16:35

Choose a tag to compare

  • Add rpc worker configs: #2542
  • Update lib err string: #2536