sBTC Research - Generating Signing Bitmap

[AshtonStephens]

This is a research discussion post meant to be edited with research notes surrounding generating the bitmap that represents the signing round approval for the signer set. Note that this terminology is likely wrong but this discussion is here to track that research once the question becomes clearer.

[AshtonStephens]

Currently under investigation by @setzeus.

[setzeus]

When reading through this my interpretation is the following:

1. When successfully inserted (either deposit/withdraw) an authorization-map should be created with the TXID as key & with at least one field as signer-set that holds a list of successful signers
2. When a signer signs, their vote is registered in the authorization-map & their principal is appended to the list of signers

It’s unclear though whether there are also additional maps required? Is it possible we need a map for UTXOs?

[setzeus]

As a follow up from meeting it's an unknown unknown whether Stacker Authorization Transaction requires:

A. A bitmap of all voters
B. A bitmap of all voters and their vote direction

[jcnelson]

The reason the signing bitmap needs both those who vote to accept and those who vote to reject is because the set of Stackers must prove that at least 70% of them by weight were online when the vote was taken. This would be the sum of those who accept and those who reject, by STX weight. This is important, because a liveness failure on the Stackers' part disables their PoX payouts and stops peg-ins until Stackers can reach quorum. We can't measure liveness if only the "yes" votes are recorded.

[xoloki]

Answered in #317

stacks-network/sbtc#317 (comment)