jferrant

Depends on https://github.com/stacks-network/stacks-core/pull/6180

Make sure to renable regr_use_block_header_pk Depends on https://github.com/stacks-network/stacks-core/pull/6180

Currently signers retrieve their sortition view from the stacks node and use this information to assess a block proposal. Instead, signers should use their global signer state to determine block...

A signer may mark a miner invalid because it has timed out, reverting to the old miner. Other signers may still see this same miner as valid because of multiple...

Requesting a block after receiving an event about it on the observer might result it the node not having processed it yet

3

There is a discrepency between the burn block processed and broadcasted by event observer and the node updating its peer info state. Saw some signer errors as a result: 08:19:26.594...

Update signers to use 2 phase commit approach to block signing. They should run a round of "Pre Commits" to indicate they are going to sign the block. If a...

There is currently a bool in MinerConfig called `replay_transactions`, but its only there for testing the tx replay functionality before making it default behaviour (currently defaults to false and is...

Given how disallow_reorg_within_first_proposal_burn_block_timing_secs_but_more_than_one_block_scenario is structured, you cannot currently gaurantee that the block has NOT already been processed by the node when calling get_peer_stacks_tip_height() causing a potential off by one race...

Create test blocks for the latest epochs to trigger the InvalidStacksBlock paths that come from converting other error variants into it.