Skip to content

Enforce BIP94 (TestNet4) difficult adjustment logic - #1329

Open
lontivero wants to merge 3 commits into
MetacoSA:masterfrom
lontivero:fix-testnet4-pow
Open

Enforce BIP94 (TestNet4) difficult adjustment logic#1329
lontivero wants to merge 3 commits into
MetacoSA:masterfrom
lontivero:fix-testnet4-pow

Conversation

@lontivero

@lontivero lontivero commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Closes #1328

Tests verify that:
1. Testnet4 uses the first block of the previous period as the difficulty anchor
2. Min-difficulty blocks (from 20-minute rule) don't distort retargeting
3. Real testnet4 block headers at difficulty boundary (28224, 30239, 30240)
SupportTaproot = true,
SupportSegwit = true,
CoinType = 1,
EnforceBIP94 = true, // Testnet4 a different difficulty adjustment rule

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is for TestNet4 and only for TestNet4. TestNet5 proposal is different so, I copied the name for bitcoin core but it is a flags that makes no much sense because it is true for only one very specific network.

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.

TestNet4: header sync fails PoW validation (Node.GetChain throws); Core 31.1 accepts the same chain

1 participant