search

stacks-network / stacks-core

The Stacks blockchain implementation
https://docs.stacks.co
GNU General Public License v3.0
3.01k stars 671 forks source link

Signer `chainstate` cache should reset when receiving proposal from unknown hash #5251

Closed kantai closed 1 month ago

kantai commented 1 month ago

If the signer binary receives a block proposal before receiving the burn block notification, its possible that their chainstate cache is out of sync.

This is the current logic in the signer for this case: https://github.com/stacks-network/stacks-core/blob/e53547ccec88208197a9977563d9d509164cfa2a/stacks-signer/src/chainstate.rs#L238-L247

This causes the signer to reject the miner's proposal.

Rather than rejecting the proposal, the signer should actually invalidate the chainstate cache, refetch it, and try again.

blockstack-devops commented 3 weeks ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.