Skip to content

Mining: similar to BIP 320, do not count the version bits miners roll for work as an unexpected version - #1091

Open
whiskyrelaxing wants to merge 1 commit into
Veil-Project:masterfrom
whiskyrelaxing:rolled-version-bits
Open

whiskyrelaxing wants to merge 1 commit into
Veil-Project:masterfrom
whiskyrelaxing:rolled-version-bits

Conversation

@whiskyrelaxing

@whiskyrelaxing whiskyrelaxing commented Oct 23, 2026 •

Copy link
Copy Markdown

Sha256d asics roll these bits through stratum version rolling, the BIP 320 mask.

@ohcee

ohcee commented Oct 30, 2026

Copy link
Copy Markdown
Collaborator

Thanks, this looks right. The mask stays clear of the algo flags and the deployment bits, and it only affects the warning. Can you add a description saying which miner or setup is rolling these bits?

@ohcee

ohcee commented Oct 30, 2026

Copy link
Copy Markdown
Collaborator

ACK 9c38dd8. Tested on regtest, master against this PR, using a local test only change so -blockversion takes effect (regtest currently ignores it). Bit 13, all of bits 13 to 23, and rolled SHA256d stop triggering the warning. Bits 12 and 27 still trigger it. Master and PR nodes sync each other’s rolled blocks in both directions with the same tip and no rejects. Not tested with stake blocks or a real rolling miner.

eRaWk23

This comment was marked as outdated.

@ohcee ohcee left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

ACK 9c38dd8, test details in my comment above.

@ohcee
ohcee dismissed eRaWk23’s stale review October 30, 2026 20:38

Superseded by a later review.

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.

3 participants