But it wasn't integrated into the signer binary yet.
The signer runloop should integrate this by holding a SortitionsView option in the RunLoop struct. Integration should be fairly straight forward -- I think roughly:
Add the sortition_state: Option<SortitionsView> field to RunLoop
On receiving a block proposal, if sortitions_view is None, reload it via fetch_view(). Then invoke check_proposal (in addition to the existing checks).
On receiving a burn block event, set sortitions_view to None.
Signer sortition state tracking was implemented in:
https://github.com/stacks-network/stacks-core/pull/4801
But it wasn't integrated into the signer binary yet.
The signer runloop should integrate this by holding a
SortitionsView
option in theRunLoop
struct. Integration should be fairly straight forward -- I think roughly:sortition_state: Option<SortitionsView>
field toRunLoop
sortitions_view
isNone
, reload it viafetch_view()
. Then invokecheck_proposal
(in addition to the existing checks).sortitions_view
toNone
.