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
There should be a boot contract (.sbtc) that stores pending sBTC operations -- the miner node will be responsible for inserting them into the contract.
We should have read only functions to retrieve all pending transactions (peg-in, peg-out, handoff)
There should be a read only function to check current state (e.g., if we haves sBTC ops older than x amount of time...this is bad state, DKG has not been set within x amount of time, etc.).
There should be a write function (only writeable by the N signers for a given reward cycle N) to set DKG
There should be a boot contract (.sbtc) that stores pending sBTC operations -- the miner node will be responsible for inserting them into the contract.
We should have read only functions to retrieve all pending transactions (peg-in, peg-out, handoff)
There should be a read only function to check current state (e.g., if we haves sBTC ops older than x amount of time...this is bad state, DKG has not been set within x amount of time, etc.).
There should be a write function (only writeable by the N signers for a given reward cycle N) to set DKG
Considering re-visiting / re-factoring / importing logic used in sbtc-registry: https://github.com/Trust-Machines/stacks-sbtc/blob/main/sbtc-mini/contracts/sbtc-registry.clar
Relates to #3948
The text was updated successfully, but these errors were encountered: