In this release, the sBTC signers switch to a new locking script for the UTXO that custodies funds.
Highlights • Images • Upgrade Instructions
✨ Highlights
- The signers will switch to a new locking script at Bitcoin block 972295.
- Introduce support for a new deposit script.
🐳 Images:
Important
Always use immutable image tags - the image digests are provided below. Verify the attestation of these images using this guide.
We publish our images on GitHub Container Registry.
sBTC Signer
- 🏷️
stacks-sbtc/sbtc:signer-v1.4.0 - 🔒
sha256:7b43d5d0005bcbeb9c7b3b90367c960ac31e8a9208977f700ce0d43eae5f3da1
Blocklist Client
- 🏷️
stacks-sbtc/sbtc:blocklist-client-v1.4.0 - 🔒
sha256:cfea33b097b04cdadae78e3a7bd9f94c22a9ae1c016fc9c65512f310cfc4739a
📙 Database migrations
Important
If you run your signer using the --migrate-db flag, the database will be applied automatically. If you do not use this flag, you must apply the migrations manually.
--migrate-db is enabled by default in our official Docker images.
Database migrations may be found at signer/migrations.
🛠️ Upgrade Instructions:
- Stop your sBTC signer
- Back up your database
- Database migrations:
- (recommended) If you run your signer with
--migrate-db, database migrations will be automatically applied upon startup, - (advanced) Otherwise, apply database migrations manually
- (recommended) If you run your signer with
- Update your sBTC images as specified above
- Restart your sBTC signer and blocklist client
📝 What's Changed
Click to expand
- feat: v2 signing scripts for deposits and signer UTXOs by @djordon-stacks in #2138
- feat: activate v2 signing in the sBTC signer by @djordon-stacks in #2149
Full Changelog: v1.3.6...v1.4.0