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