How to Run an sBTC Signer
Last updated
Was this helpful?
Last updated
Was this helpful?
Each sBTC signer will control a set of signing shares used to sign transactions on both Bitcoin and Stacks.
Such shares will be encrypted by using the private_key
specified in the Signer's config and stored in the PostgreSQL database attached to each signer.
It is of the utmost importance to:
Prevent unauthorized access to the sBTC Signer infrastructure (the signer itself, its private key, and the associated PostgreSQL database);
keep an offline, secure backup of the sBTC Signer private key;
regularly backup the PosgreSQL database and store it in a secure location.
See for additional best practices to run an sBTC signer.
Below are the minimum required specs to be able to run a sBTC signer.
2 CPU
4GB memory
50GB storage
Note that these are in addition to the hardware requirements for running a Stacks node and Bitcoin node outlined in the .
You will need bitcoind
version 25 or higher.
Your Bitcoin node must include these settings for sBTC signer operation:
txindex=1
: Transaction indexing must be enabled
server=1
: RPC server must be enabled
zmqpubhashblock=tcp://*:28332
: ZMQ block hash notifications
zmqpubrawblock=tcp://*:28332
: ZMQ raw block notifications
The ZeroMQ configuration specified above enables real-time blockchain event notifications from Bitcoin Core to the sBTC signer.
The two required ZMQ endpoints serve distinct purposes:
zmqpubhashblock
: Broadcasts only block hashes for lightweight block detection
zmqpubrawblock
: Broadcasts complete block data for transaction processing
This notification system creates a direct event stream when:
Bitcoin Core validates a new block
Block data publishes via ZMQ
Signer processes relevant sBTC transactions
Please ensure your Stacks version is up-to-date (using the latest release).
You will need to add a new event observer that relays information from the sBTC smart contracts to the sBTC signer:
The signer configuration file (signer-config.toml
) defines the signer's operation parameters. The configuration sections include:
Defines how the signer connects to Bitcoin Core:
Defines the signer's identity and network participation:
Controls how the signer communicates with other network participants:
The signer operates on port 4122 by default and supports both TCP and QUIC protocols for peer communication. The signer will attempt QUIC connections first for improved performance, automatically falling back to TCP if QUIC is unavailable or blocked on the network.
Monitoring Details TBD
Troubleshooting Guide TBD
See .
See .
See for a Docker Compose including all the required components.