Skip to content

Testnet reset: the Babbage epoch - #2169

Open
nullPointerEnjoyer wants to merge 8 commits into
masterfrom
testnet-babbage
Open

nullPointerEnjoyer wants to merge 8 commits into
masterfrom
testnet-babbage

Conversation

@nullPointerEnjoyer

Copy link
Copy Markdown
Collaborator

Summary

Resets the testnet as the Babbage epoch, named after Charles Babbage, continuing from the Lovelace testnet (the first program was written by Ada Lovelace for Babbage's Analytical Engine).

  • Fresh genesis: the genesis message changes to babbage (keys, timestamps and output structure unchanged), giving a new chain id. The initial supply is minted at 40 trillion TML, sized so faucet airdrops of one minimum stake pledge (40,000 TML) per tester can never crowd out the supply while staking is exercised.
  • New network magic bytes (BABB1871): old and new testnet nodes refuse each other at handshake, so there is no split-brain ambiguity during the transition.
  • All upgrades active from genesis: the six historical testnet fork heights are collapsed — consensus starts at PoS V1 (maturity 7200) at height 1, and the chainstate upgrade list is the fully-tightened final state (orders V1, sighash commitments V1, token id generation V1, the consensus-tightening rules, etc.) from height 0. This is exactly the configuration mainnet launched with, and equals the old testnet's post-fork state minus the history.
  • Checkpoints restart with the new genesis id at height 0.
  • The wasm JS test suite drops its hardcoded testnet fork heights (V0-side encodings are unreachable now; V0 remains covered by the Rust tests and mainnet).

Testnet operators must resynchronize from scratch; old testnet data, checkpoints and bootstrap files do not apply. The seed infrastructure is redeployed with 1.5.0 nodes as part of the release.

Notes

  • Field-by-field, the collapsed upgrade list equals the previous post-fork-6 testnet state (verified in review).
  • The genesis stake pool keeps the same faucet/staker keys as before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant