Skip to content

Conversation

@sandtreader
Copy link
Collaborator

One early SPO used a testnet address (e0...) as its reward account, and registered the same hash on mainnet (e1...). It still got its reward in epoch 211 so this must have been accepted! Previously we ignored the network Id for comparison/mapping, but since we switched to StakeAddress everywhere, this broke.

This PR forces the network ID in map_parameters(), and adds a bunch of debug. Note that StakeAddresses are now Display'ed including the leading network/type byte, which would have made this easier to find!

One early SPO used a testnet address (e0...) as its reward account,
and registered the same hash on mainnet (e1...).  It still got
its reward in epoch 211 so this must have been accepted!
@sandtreader sandtreader requested a review from lowhung October 28, 2025 17:49
@sandtreader sandtreader linked an issue Oct 28, 2025 that may be closed by this pull request
@sandtreader sandtreader merged commit 465b906 into main Oct 28, 2025
2 checks passed
@sandtreader sandtreader deleted the prc/303-missing-spo-rewards branch October 28, 2025 22:40
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.

Missing SPO reward in epoch 211

4 participants