docs: v6.6.0 catch-up — HELD, needs rework (verified subset in #59) - #56
Draft
seidroid[bot] wants to merge 82 commits into
Draft
docs: v6.6.0 catch-up — HELD, needs rework (verified subset in #59)#56seidroid[bot] wants to merge 82 commits into
seidroid[bot] wants to merge 82 commits into
Conversation
…s becomes a config field with new default behavior, and internal RouterOptions replace MaxPeers/MaxConnected/MaxConcurrentDials/MaxOutboundConnections with new MaxInbound/MaxOutbound semantics affecting connection limits. (sei-protocol/sei-chain#3037)
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
…uture/non-existent numeric block heights instead of an error, and eth_getProof now works across additional store backends (tracekv, Giga cache, prefix stores) instead of only classic IAVL. (sei-protocol/sei-chain#3119)
…ctionCountByHash JSON-RPC methods now return a count consistent with eth_getBlockByNumber, filtering out EVM txs without a receipt and including wasm/bank transfer transactions. (sei-protocol/sei-chain#3125)
…ceBlockByNumber and debug_traceBlockByHash when using the default (struct) tracer, changing internal execution behavior while keeping the same RPC surface. (sei-protocol/sei-chain#3058)
…e-lattice-hash) were removed from the state-commit config template, and a new validation rule now requires lattice hash to be enabled when using split_write mode. (sei-protocol/sei-chain#3128)
… from 5% to 0% since the Oracle Price Feeder is retired, altering default slashing behavior. (sei-protocol/sei-chain#3157)
…ommend migrating to SeiDB to avoid data corruption or panic. (sei-protocol/sei-chain#3159)
…ests by forwarding only allowed elements and merging responses by id, and reduces the legacy HTTP body limit from 32MiB to 5MiB to match go-ethereum's default. (sei-protocol/sei-chain#3160)
…datory; nodes will panic if sc-enable is false, and several IAVL-related CLI commands and config fields have been removed. (sei-protocol/sei-chain#3146)
…ce` (default false) that gates the parallelized default debug_traceBlock* path. (sei-protocol/sei-chain#3187)
…nfinite re-entry: a tx that fails during block execution is allowed one retry, but subsequent failures leave it in the cache and cause CheckTx to reject re-submission. (sei-protocol/sei-chain#3200)
…e Autobahn (GigaRouter) feature, which loads validator committee and consensus/producer parameters from a JSON config file; setting a remote validator signer (priv-validator.laddr) is incompatible with Autobahn. (sei-protocol/sei-chain#3194)
…t store config (defaulting to true and required to remain true, as setting it false panics), plus internal benchmark/metrics changes. (sei-protocol/sei-chain#3081)
…he `filter-peers` config option and removing the `/p2p/filter/addr` and `/p2p/filter/id` ABCI query paths. (sei-protocol/sei-chain#3225)
…lting to "pebbledb") that enables a Pebble-backed tx_hash→block_number index for faster receipt-by-hash lookups on the parquet receipt store, replacing the previously unsupported `disable-tx-index-lookup` field. (sei-protocol/sei-chain#3222)
… generate Autobahn (GigaRouter) JSON config from node pubkey files, along with side-effect files (validator_pubkey.txt, node_pubkey.txt) now written when keys are saved. (sei-protocol/sei-chain#3220)
…pt store retention is now always derived from the global `min-retain-blocks` flag. (sei-protocol/sei-chain#3237)
…xMempool and disable the mempool, consensus, statesync, and blocksync reactors, introducing hard block limits (max 2000 txs, ~2MB total) and changing behavior when the autobahn config is enabled. (sei-protocol/sei-chain#3224)
….0 batch rules: notifications (requests without an id) produce no entry in the batch response, and when there would be no response objects the server returns an empty HTTP body instead of an empty JSON array. (sei-protocol/sei-chain#3246)
…, sc-enable-lattice-hash) for Giga Storage and a GIGA_STORAGE env var that toggles FlatKV SC dual-write plus EVM SS split-read/write modes, along with EVM store iteration support. (sei-protocol/sei-chain#3268)
…_priority_hash_height) are exported every 1024 blocks so node operators can detect ProposerPriority divergence between validators. (sei-protocol/sei-chain#3277)
…true instead of false, changing the default behavior of generated autobahn configs. (sei-protocol/sei-chain#3234)
…Logs now return an empty array ([]) instead of null when no logs match or a bounded filter's range is exhausted, aligning with the Ethereum JSON-RPC spec. (sei-protocol/sei-chain#3292)
…C methods (traceTransaction, traceTransactionProfile, traceBlockByHash, traceCall, traceStateAccess) in addition to traceBlockByNumber, so requests targeting historical blocks beyond the configured lookback are now rejected with an error. (sei-protocol/sei-chain#3515)
…ons via a direct mempool EVM-hash index instead of paginating unconfirmed txs, and the UnconfirmedTxs RPC now returns results from a recent mempool snapshot with byte totals computed over that snapshot rather than the full mempool size. (sei-protocol/sei-chain#3546)
… field and the block payload/producer config are restructured (total_gas split into wanted/estimated), plus some RPC behaviors change under the Autobahn mempool. (sei-protocol/sei-chain#3522)
…ec, Int, Uint) and the JSON precompile's ExtractAsUint256, causing overly long numeric strings to now be rejected with an error. (sei-protocol/sei-chain#3532)
…that swallows most halting consensus validation failures, plus a new sei_unsafe_validation_skipped_total metric emitted by non-default build variants. (sei-protocol/sei-chain#3429)
…ei_chain', which alters exported metric names that operators query in monitoring dashboards. (sei-protocol/sei-chain#3554)
…ommit mode (sc-write-mode = "flatkv_only") and fixes snapshot/state-sync and empty-value WAL-replay correctness for FlatKV-only nodes. (sei-protocol/sei-chain#3545)
… HTTP write timeout, defaulting to 30s, replacing the previous auto-adjustment logic tied to timeout-broadcast-tx-commit. (sei-protocol/sei-chain#3558)
…-num-blocks) are now deprecated with no effect, and BroadcastTxCommit now honors the configured timeout-broadcast-tx-commit setting. (sei-protocol/sei-chain#3567)
…rage keys, rejects malformed keys, and enforces a maximum of 1024 storage keys per request. (sei-protocol/sei-chain#3556)
…alidation_error` (and the `evidence_overflow` value became `too_much_evidence`) on the sei_unsafe_validation_skipped_total counter emitted by non-default (mock) build tags. (sei-protocol/sei-chain#3565)
…fig fields have been removed; pebbledb is now the only supported receipt-store backend. (sei-protocol/sei-chain#3580)
…set (MaxOffset=10000), and scan iterations (MaxScanLimit=10000), and no longer auto-enables count_total when limit is omitted — requests exceeding these bounds return InvalidArgument errors. (sei-protocol/sei-chain#3494)
… list are now rejected with an 'auth list cannot be empty' validation error. (sei-protocol/sei-chain#3528)
…h_getBlockTransactionCountByHash now return a 'receipts have been pruned' error when the requested block height is below the receipt store's earliest available version. (sei-protocol/sei-chain#3216)
…alidators and adds wire-format size/count limits on protobuf message fields, which affects network compatibility and validator set sizing. (sei-protocol/sei-chain#3609)
…hether the Unsafe*TimeoutOverride fields are applied, changing when timeout overrides take effect on nodes. (sei-protocol/sei-chain#3601)
… that limits the time allowed to read HTTP request headers (mitigating slowloris attacks), defaulting to 10 seconds. (sei-protocol/sei-chain#3607)
…of results returned by the `tx_search` and `block_search` endpoints (default 10,000), which changes their behavior on nodes. (sei-protocol/sei-chain#3608)
…mpute a backend-independent digest of EVM logical state, letting operators compare memIAVL and FlatKV nodes at the same height. (sei-protocol/sei-chain#3611)
…usted absolute path with SHA-256 verification, and a new SEI_EVMONE_LIB_DIR environment variable lets operators override the library directory. (sei-protocol/sei-chain#3624)
…iles (addr, bank, distribution, gov, ibc, json, oracle, p256, pointer, pointerview, solo, staking), and the oracle precompile is now retired so getExchangeRates and getOracleTwaps revert with an error. (sei-protocol/sei-chain#3625)
These 10 files were reviewed against sei-chain at v6.6.0 and found clean, so they are landing separately in #59 where they are not blocked by the defects in the rest of this PR. Reverted here to keep the two PRs disjoint — they can merge in either order. evm/evm-parity/{evm-compatibility,gas-and-fees,state-proofs, transaction-types,websocket}.mdx evm/precompiles/json.mdx evm/transactions.mdx learn/twin-turbo-consensus.mdx node/rocksdb-backend.mdx node/seictl.mdx What remains here carries 22 blocking findings and needs rework, not review.
monty-sei
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Auto-generated from the 392 PRs in sei-chain
v6.5.2..v6.6.0. A full review against sei-chain at tag v6.6.0 produced 141 findings, 22 of them blocking. What remains in this PR is the portion carrying those defects.Why this needs rework rather than review
The defects are systemic, not a fix-list. The bot writes from individual PR diffs and never reconciles against the release tip, so it documents:
tx-index-backend, added by #3222 and removed by #3580 — both listed under## v6.6)evm-ss-modeappears nowhere in the tree; the real key is the booleanevm-ss-split)Several pages contradict themselves 100 lines apart.
The most dangerous finding
node/technical-reference.mdxfuses two changes with different first-ship tags under one "As of v6.5": it saysstateless-leader-electiondefaults to true and is now inert, "setting it tofalseno longer has any effect."The default flip is v6.5.0. The inertness is v6.6.0 only —
round_state.gocarries 3 live references at v6.5.2 and 0 at v6.6.0. A v6.5.x operator following this removes their validator from consensus. v6.5.2's own config comment warns about exactly this in capitals.Categories of blocking defect
tx-index-backend,evm-ss-mode,sc-read-mode,sc-enable-lattice-hash,max_gas_per_block[state-store.receipt-store];sc-write-modeunder[state-store]instead of[state-commit]enable-pebble-metrics = false— source default is truecrisis_end_blocker_duration,crisis_init_genesis_unmarshal_duration,app_pending_nonce_totalTxMempool; it is the reverseRecommended bot fixes
Coverage caveat
The review was not exhaustive. The nine
node/*.mdxfiles were checked twice, claim-by-claim.learn/(4 files, ~430 lines) was reached only by a single completeness sweep, which found six defects on first contact — the real count is likely higher.evm/*coverage was partial.