Skip to content

dgb: G3b FULL PASS — dual-path won-block leg on genuinely taproot-ACTIVE regtest - #535

Merged
frstrtr merged 1 commit into
masterfrom
dgb/g3b-taproot-active-won-block-dualpath
Jun 26, 2026
Merged

dgb: G3b FULL PASS — dual-path won-block leg on genuinely taproot-ACTIVE regtest#535
frstrtr merged 1 commit into
masterfrom
dgb/g3b-taproot-active-won-block-dualpath

Conversation

@frstrtr

@frstrtr frstrtr commented Jun 26, 2026

Copy link
Copy Markdown
Owner

Closes the G3b transition leg (integrator UID2612): c2pool-dgb FOUND+ASSEMBLED+ACCEPTED a witness-bearing won block via BOTH paths on a net where taproot reached ACTIVE through GENUINE BIP9 signaling.

Captured PASS (master @350040182 c2pool-dgb, digibyte 8.26.2 regtest)

G3B_DUALPATH_TAPROOT_ACTIVE result=PASS tap_active_height=580 lockin_signaled=144 threshold=108 \
  armA_p2p=22ac96c9f2232799680c0b8a3599eaf9d66ff04613684196690cc9b4ad2aa317 \
  armB_submitblock=b89f93339d5fa60388adf613e64555262585b6c3d795a78a99afa47a17e6f15f

Scope

Fenced/additive: scripts/ only. No consensus, shared-base, build.yml or CMake surface. Per-coin isolation: DGB only, localhost, self-service creds, ports outside the bitcoin-family regtest band. Composes #534 (activation) + #458 (segwit won-block assembly); FAILS on a pre-#82 binary (ARM B stub) or non-activated net (E/G).

No self-merge — integrator merges on operator push approval.

…IVE regtest

Composes the two already-proven G3b harnesses to close the milestone
integrator named as the actual G3b PASS: a c2pool-dgb-assembled won block
must reach the network via BOTH the embedded P2P on_block_found path AND the
submitblock RPC fallback, run on a net where taproot reached ACTIVE through
GENUINE BIP9 signaling (not the regtest always-active default).

PHASE 1 reuses the #534 anti-cheat activation (-vbparams genuine BIP9 window;
stock 108/144 threshold/window untouched): S0 taproot DEFINED at genesis,
defined->started->locked_in->active driven by mined bit-2 blocks, lock-in
count asserted >= the stock 108 threshold.

PHASE 2 reuses the #458 segwit won-block assembly: a witness-bearing tx is
driven through the c2pool-dgb won-block path; the won block must carry the
BIP141 coinbase commitment and be ACCEPTED by peer node B. Run twice — ARM A
(embedded P2P on_block_found) and ARM B (--no-p2p-relay -> submitblock RPC
fallback) — to close the dual-path gate.

New assertions beyond #458 (E/G): the accepting peer enforces ACTIVE taproot
consensus (getdeploymentinfo taproot.active=true) at the won-block height, so
the block is provably valid under real active-taproot rules.

Fenced/additive: scripts/ only. No consensus, shared-base, build.yml or CMake
surface. Per-coin isolation: DGB only, localhost, self-service creds, ports
outside the bitcoin-family regtest band.
@frstrtr
frstrtr merged commit 12db5aa into master Jun 26, 2026
32 checks passed
@frstrtr
frstrtr deleted the dgb/g3b-taproot-active-won-block-dualpath branch June 26, 2026 13:34
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