feat(recovery): v1.6.2 incident recovery, EVM GHSA hotfix, peer-broadcast fix - #93
Merged
Conversation
Squash of three v1.6.2-prep commits (previously b87bd40, 006b4a4, 667af53): - fix(app): treat a duplicate broadcast (Comet code=19, "tx already in mempool") as normal rather than a failure, and collect batch failures instead of aborting the whole batch on the first bad tx. Added a table test covering the three node responses. - docs(changelog): condense the v1.6.0/v1.6.1 changelog to symptom, cause and fix; the peer-broadcast work becomes a single entry. - chore(upgrade): register an empty v1.6.2 upgrade handler for a binary-level version bump carrying no state migration. go.mod points cosmos/evm at the local ../evm fork for this build.
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.
Release v1.6.2.
app/hardforks/aug2026): supply-neutralPreBlocker (
mint == burn), gated by chain-id + height (mainnettacchain_239-1@ 24671476), guarded and aborts on any mismatch. Verified onthe real mainnet halt-state.
app/app.go): recover sender + build viaMsgEthereumTx.BuildTx, treat "already in mempool" as OK, don't fail the whole batch.gen_localnode.shstrayexit, changelog.