Skip to content

dgb: conform address_p2sh_version2 to oracle (drop LTC-borrowed =5 -> 0) - #150

Merged
frstrtr merged 1 commit into
masterfrom
dgb/p2sh-version2-conform-r
Jun 18, 2026
Merged

dgb: conform address_p2sh_version2 to oracle (drop LTC-borrowed =5 -> 0)#150
frstrtr merged 1 commit into
masterfrom
dgb/p2sh-version2-conform-r

Conversation

@frstrtr

@frstrtr frstrtr commented Jun 18, 2026

Copy link
Copy Markdown
Owner

Closes the last prescan-DGB conformance gap on master.

address_p2sh_version2 (secondary/parse-leniency P2SH prefix) was carrying =5, an unconsumed LTC-borrowed value. Oracle frstrtr/p2pool-dgb-scrypt accepts only {30,63}; conform to 0 for both nets. Parse-leniency only, NOT used for output/consensus — no consensus impact, byte-conformant to oracle.

  • 1 file (src/impl/dgb/params.hpp), GPG-signed 7c4ea81, cherry-pick of e16602f rebased onto master d5879c9.
  • build c2pool-dgb EXIT=0.
  • 3-bucket: COMPAT/isolation-adjacent; conforms to own oracle.

HOLD merge — integrator merges on operator push-approval.

…et 0)

The oracle frstrtr/p2pool-dgb-scrypt (IDENTIFIER 4B62545B1A631AFE) accepts
exactly {ADDRESS_VERSION=30, ADDRESS_P2SH_VERSION=63} in bitcoin/data.py and
defines no secondary P2SH prefix. The prior mainnet =5 was an LTC-borrowed
artifact (LTC had a real P2SH migration; DGB did not) and is unconsumed in
src/. Set 0 on both nets so the address SSOT matches the oracle exactly.
Resolves the last open prescan-DGB [confirm-vs-oracle] item.

(cherry picked from commit e16602f)
@frstrtr
frstrtr merged commit 6c1f7c1 into master Jun 18, 2026
16 checks passed
frstrtr added a commit that referenced this pull request Jun 18, 2026
…ded-body lane — non-destructive, BCH-only ahead
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