Accept version-one ledger transition - #9
Merged
Conversation
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.
Linked work
Closes #6
Outcome
Version-one M1 genesis, native transfer, fee routing, replay/expiry handling, receipts, and ordered atomic block execution now have an accepted canonical specification, devnet parameter ADR, frozen vectors, and independent C++20/Python decision harnesses.
Scope
No production kernel, persistence, networking, consensus adapter, production tokenomics, or deployment is included.
Protocol and compatibility impact
ADR 0006 and
ledger-transition-v1.mdare consensus-visible and accepted under the standing delegation. Version-one bytes, result numbers, validation order, writes, and failure atomicity are immutable. Future fee, issuance, account-lifecycle, or receipt changes require a new version and migration evidence.Verification
Each command passed 4/4 CTest tests:
PROTOCOL_STACK_PRESET=gcc-debug tools/verify.shPROTOCOL_STACK_PRESET=gcc-sanitizers tools/verify.shPROTOCOL_STACK_PRESET=clang-debug tools/verify.shPROTOCOL_STACK_PRESET=clang-sanitizers tools/verify.shThe vector set covers success, replay, self-transfer, recipient creation, zero amount, low fee, expiry, absent sender, nonce mismatch/exhaustion, debit overflow, insufficient balance, invalid signature, wrong chain, truncation, unknown kind/unauthorized mint surface, ordered receipts, roots, header, and block ID. JSON, TOML, YAML, Python bytecode, shell syntax, Markdown links, and
git diff --checkalso passed.Risks and follow-up
The numerical values are M1 devnet parameters, not frozen production tokenomics. Issue #8 implements the production in-memory kernel, frozen-vector reuse, fuzz targets, invariant tests, and at least 10,000 seeded differential sequences.
Checklist
current-state.mdare accurate.