[DRAFT, DO NOT MERGE] chore(genesis): activate senderBlacklist fork on testnet at block 94550000#144
Draft
lockchainco wants to merge 1 commit into
Draft
Conversation
…50000 Follow-up to the testnet code PR #143 (merged). Sets the activation block for the senderBlacklist consensus fork. Current testnet head ~94,498,427 + ~52,000 blocks = ~28 hours of margin at testnet block rate. DO NOT MERGE UNTIL ALL TESTNET VALIDATORS ARE ON THE PATCHED BINARY. server.go performs a strict AllForksEnabled membership check on every genesis fork name at startup; any validator on the old binary against this genesis hard-errors with `fork is not available: senderBlacklist`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0184d2b to
123f910
Compare
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
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.
This is the operational follow-up to the merged code PR #143. Sets the activation block for the
senderBlacklistconsensus fork on testnet.senderBlacklistchain/public-configs/genesis-testnet.json⛔ Hard rollout prerequisite — binary-first, then genesis
server.goperforms a strictAllForksEnabledmembership check at startup. Any validator running an unpatched binary against a genesis carryingsenderBlacklistwill hard-error with:and refuse to start. So this PR can only safely merge after all testnet validators are on the patched binary (commit
8e3a6963ontestnetbranch).Operational checklist (for the user — driven manually)
hydral1/hydragon-docker:patched-2026-05-15(or similar tag) containing the mergedtestnetbranch.genesis-testnet.json. The activation block (94,550,000) is still in the future, so behaviour stays unchanged until then.rejected transaction from consensus-blacklisted senderaround block 94,550,000 and beyond. Verify no chain halt, no fork-off, control wallets still mining.2/3 invariant reminder
Once the fork is active, if the patched fraction of the active validator set drops below 2/3, the chain halts (no quorum on any block containing a blacklisted-sender tx that an unpatched proposer keeps including). This is by design — better halt than admit. Avoid pulling patched validators out of the set post-activation.
🤖 Generated with Claude Code