sBTC implements the SIP-010 token standard and enables the minting, burning, locking, and unlocking of sBTC tokens. The Peg-in sBTC Signer API facilitates the signing of peg-in requests by Stackers to approve the transfer of Bitcoin into the sBTC system.
sBTC is a protocol and therefore has no particular intrinsic technical requirements, however, different reference implementations of the protocol may have different requirements. Generically, a network-connected VM with an 100Mb/s network and 95% uptime should be sufficient to participate in the protocol.
The architecture is explained in the sBTC technical docs.
Testing a protocol is very different from testing a typical software product.
The strategy in sBTC is to break the final sBTC application into two deliverables to test the different aspects of the protocol.
- Release a custodial version of the protocol to test the user interface of sBTC.
- Release a non-consensus breaking version of the protocol to allow testing of operator implementations.
First let’s define what a deployment is for a protocol. We define a deployment of an sBTC version as:
- A smart contract deployed on the Stacks blockchain defining an sBTC SIP-010 token.
- Documentation explaining the protocol, and how to interact with the sBTC token as well as how to participate in the network.
- Published reference implementations of any software binaries and tools needed to participate in the protocol as a user or operator.
The plan is to deploy the following versions:
- sBTC Alpha: A custodial version of the protocol maintained by a single entity, to support an initial version of the sBTC interface
- sBTC Mini: A decentralized version of the protocol without any consensus-breaking changes
- sBTC MVP: A consensus-breaking decentralized version with a minimal feature set
- sBTC 1.0: The first version of the protocol which is economically sound, decentralized and secure
All operations on sBTC are visible on-chain, but there are no plans currently for a hosted sBTC dashboard.