You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The old stacks-sbtc repo is currently somewhat of a problem. It represents the old sBTC Alpha design, which has been superseded by the new Alpha Romeo developer release, and only bears passing resemblance to the final Nakamoto sBTC.
So we would like to get rid of stacks-sbtc, but there are external collaborators who use it to learn how to use wsts to sign taproot bitcoin transactions.
To solve this dilemma, take the frost_btc code from stacks-sbtc/frost-test/tests/frost-btc and reimplement it using the state machines as per the test_process_inbound_messages test in wsts::state_machine::test. It will be necessary to pull in a minimal amount of code from stacks-sbtc/test-utils/src/lib.rs, specifically the BitcoinProcess and generate_wallet code, while trying to avoid the SignerHelper code.
Doing this task will not only allow the removal of stacks-sbtc, but also be an excellent primer on the current state machine design of stacks-signer.
The text was updated successfully, but these errors were encountered:
Trust-Machines#24)
* fill out readme; use readme as crate level documentation; add comments for all modules; start filling in docs for point functions
* fill in rest of doc comments
* make shell snippets single line
---------
Co-authored-by: Joey Yandle <xoloki@gmail.com>
The old
stacks-sbtc
repo is currently somewhat of a problem. It represents the oldsBTC Alpha
design, which has been superseded by the newAlpha Romeo
developer release, and only bears passing resemblance to the finalNakamoto sBTC
.So we would like to get rid of
stacks-sbtc
, but there are external collaborators who use it to learn how to usewsts
to signtaproot
bitcoin transactions.To solve this dilemma, take the
frost_btc
code fromstacks-sbtc/frost-test/tests/frost-btc
and reimplement it using the state machines as per thetest_process_inbound_messages
test inwsts::state_machine::test
. It will be necessary to pull in a minimal amount of code fromstacks-sbtc/test-utils/src/lib.rs
, specifically theBitcoinProcess
andgenerate_wallet
code, while trying to avoid theSignerHelper
code.Doing this task will not only allow the removal of
stacks-sbtc
, but also be an excellent primer on the current state machine design ofstacks-signer
.The text was updated successfully, but these errors were encountered: