BTC G3b: --tuned mode produces real POPULATED parent+merged block (gate-decoupled) - #479
Merged
Conversation
…d block on isolated regtest net build_block was coinbase-only with no merged-mining marker, so even on a tuned net it could not exercise G3b parent+merged. Add build_populated_merged() (folds template mempool txs into the merkle root + a 0xfabe6d6d AuxPoW commitment in the coinbase) and a --tuned run mode that submitblocks to an isolated regtest node. Gate-decoupled: no testnet3 IBD and no SHA256d rig needed; the node is the oracle (submitblock rejects malformed blocks -> fail-closed). Validated on regtest: ACCEPTED ntx=2 mm_marker=True. --dry-run/--live unchanged.
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.
G3b deliverable is a POPULATED, parent+merged block. The existing harness build_block is coinbase-only with no merged-mining marker, and --live can only ever grind on testnet3 (rig+IBD gated). This adds a --tuned mode that produces the real artifact on an isolated regtest net, decoupled from BOTH gates.
What it does:
Fail-closed: the node is the oracle; submitblock rejects any malformed block, so this cannot false-green. --dry-run and --live paths are unchanged.
Validation (isolated regtest, VM420):
Live testnet3 ARM B remains IBD-gated (progress ~0.773, self-clearing) and ARM A rig-gated (#387/#388); this PR unblocks the POPULATED+merged proof without waiting on either. Held for tap; I do not self-merge.