read hashReserved from disk#2931
Conversation
|
ZenCash is actually affected by this as we've had some blocks from a pool that is misconfigured with BTG settings (block height in The blocks pass intial sync and Daemon failure: Debug log: |
|
This problem was effecting the Hush network as well, we are seeing hashReserved = Hush block number, which seems to indicate that people are potentially using BTG mining software to mine on other Equihash coins, not realizing that BTG changed their Equihash headers. Thanks for the patch @jc23424 👍 |
Dukeleto's zcash#2931
daira
left a comment
There was a problem hiding this comment.
utACK. Needs a test -- ideally for 1.0.15, but not having a test should not block this PR for 1.0.15 IMHO.
|
📌 Commit 15fb13f has been approved by |
read hashReserved from disk This fixes a bug where the hashReserved field of the block header is not properly read back into CBlockIndex when loaded from disk. This happens to cause no issues currently because hashReserved has always been its default value (== 0), but if a block were ever mined where this was not the case, headers read back from disk would appear to have an invalid solution
Update version string Pull in select 1.0.15 Zcash fixes: read hashReserved from disk zcash#2931 improve sync performance by increasing default value of dbcache. zcash#2873 z_importviewingkey fix from leto/zero/pull/1 Update README.md throughout, particularly the addnode addresses, plus add a sample zero.conf to ./contrib
This fixes a bug where the hashReserved field of the block header is not properly read back into CBlockIndex when loaded from disk. This happens to cause no issues currently because hashReserved has always been its default value (== 0), but if a block were ever mined where this was not the case, headers read back from disk would appear to have an invalid solution