Repository navigation
v0.8.8: chain-22 open validator mint — FORK AT BLOCK 140 000 (faucet allow-lists lifted) - #202
Merged
Merged
Conversation
…HAIN_22_OPEN_MINT_HEIGHT) Owner's decision 2026-11-22: on chain 22 any key that runs a validator may mint RAND for itself. From the activation height H the ledger's Mint arm no longer reads staking.faucet_recipients (FaucetRecipientNotAllowed) or staking.faucet_minters (MinterNotAllowed). The faucet switch, FAUCET_MAX_UNITS, the per-epoch budget, the register row (MinterNotValidator), the signature and the value rule all still bind, and admission_by_vote still gates the register. Below H nothing changes. - core: staking::OPEN_MINT_ACTIVATIONS keyed by genesis hash (chain 22 only), CHAIN_22_OPEN_MINT_HEIGHT = u64::MAX placeholder (TODO operator); Ledger::open_mint_from / open_mint, set by Genesis::build after the hash exists (genesis file and hash unchanged). - node: reload_ledger_from restores it; pool policy minter_not_allowed and rand_mint / rand_status.faucet (faucet_refusal_at) follow the height; FaucetRecipientNotAllowed no longer cached as permanent. - tests: ledger below/at/after H, caps and budget, no-activation chains; pool and faucet_refusal_at; chain-22 genesis file carries the activation. - docs: staking.md, rpc.md, deploy.md, CHANGELOG, docs/releases/v0.8.8.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GFs5gyuBMf1nCmyHCP3AT8
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
….8.8 FORK: CHAIN_22_OPEN_MINT_HEIGHT = 140_000 (was the u64::MAX placeholder). From chain 22 block 140 000 both faucet allow-lists (faucet_recipients, faucet_minters) are lifted; set 2026-11-22 at tip 73 774 (02:54Z, ~0.866 blocks/s), expected ~2026-11-23 00:08Z. Every host must run v0.8.8 before that height; before it v0.8.7 and v0.8.8 agree on every block, so the roll is host by host. - Workspace version 0.8.8: Cargo.toml, the seven workspace crates in Cargo.lock, the rand_getVersion test. - CHANGELOG: v0.8.8 section (fork height in its heading); v0.8.7 dated. - README release table, docs/deploy.md and docs/releases/v0.8.8.md name the height. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GFs5gyuBMf1nCmyHCP3AT8
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.
Owner's decision (2026-11-22): on live chain 22, any address can mint RAND for itself if it runs a validator node.
Rule
From activation height
H, the ledger'sAction::Mintvalidation stops enforcing both genesis lists:staking.faucet_recipients(FaucetRecipientNotAllowed)staking.faucet_minters(MinterNotAllowed)These still hold:
faucet: trueFAUCET_MAX_UNITS(100 RAND per mint)faucet_budget_per_epoch(10 000 RAND)MinterNotValidator)mint_commitmentvalue ruleadmission_by_vote, which still decides who gets a register rowBelow
Hthe old rules apply exactly. The genesis file and genesis hash do not change.Mechanism
The repo has no earlier height-activated rule on a running chain to copy. Every earlier rule change was "genesis-gated at the next cut". The closest pattern is a genesis parameter on the ledger that
reload_ledgerrestores, plus a build-time table keyed by genesis hash (likeCHAIN_CONSTRAINT_SETS). I followed that:ledger::staking::OPEN_MINT_ACTIVATIONSlists(chain id, genesis hash, height). It is keyed by genesis hash, so a devnet that reuses chain id 22 is unaffected. It has one row: chain 22 →CHAIN_22_OPEN_MINT_HEIGHT.CHAIN_22_OPEN_MINT_HEIGHT = u64::MAXis a marked TODO for the operator. A build carrying the placeholder behaves exactly like v0.8.7 on chain 22.Ledger::open_mint_from/Ledger::open_mint()compare againstheight, the block being applied. The field is outside the state root and equality, likerefuse_panicked_invokes.Genesis::buildsets the field once the genesis hash exists.node::reload_ledger_fromrestores it on every restart.Node consistency
admission::minter_not_allowed(genesis-validator minters) steps aside onceledger.open_mint()is true.rand_mint/rand_status.faucet/rand_getEmission.faucet. These go through the newadmission::faucet_refusal_at. FromH, a validator with a register row servesrand_mint.publish_statusre-reads the flag each commit, so it flips atH.FaucetRecipientNotAllowedis removed fromis_permanent, because it now depends on the height. A cached refusal from belowHwould censor the same bytes afterH.rand faucetCLI has no client-side allow-list check; it just callsrand_mint. Nothing to change there.Tests
staking.rs. BelowH, and at any height with no activation, an unlisted recipient or an unlisted bonded minter is refused exactly as before, at validate and at apply, with the ledger untouched. At and afterH, a bonded unlisted validator mints to an unlisted key. A key with no row is stillMinterNotValidator.MintTooLarge,FaucetBudgetExhaustedandFaucetDisabledstill bind. A second test checks the table contents.admission.rs. Pool admission flips atH, and a stranger is still refused. Also coversfaucet_refusal_at, and moves the permanence classification.constraint_set.rs. The activation row is a listed chain-22 row.deploy/genesis-chain22.jsonstill hashes to29d67542…and its ledger carries the activation. Every other committed genesis carries none.Not built or tested locally (workspace too large for the Mac); relying on CI.
Docs
docs/staking.md,docs/rpc.md,docs/deploy.md,CHANGELOG.md(Unreleased), and a draft ofdocs/releases/v0.8.8.md.Before tagging
CHAIN_22_OPEN_MINT_HEIGHT. At about 1 block/s,Hmust be far enough past the tip for the 25-host roll. Chain 22 was at about 72 450 on 2026-11-22.H.FaucetWithBridgecheck is unchanged.🤖 Generated with Claude Code
https://claude.ai/code/session_01GFs5gyuBMf1nCmyHCP3AT8