This maintenance release includes security hardening improvements and operational enhancements.
Highlights • Images • Upgrade Instructions
✨ Highlights
- Scope sighash authorization to the Bitcoin block hash during which it was approved.
- Make signature gathering a one-shot process for v1 signatures.
🐳 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.1 - 🔒
sha256:acfd6263d18a474d68d8950d1d06fd203dc217f70dac95515b445fd4decf7760
Blocklist Client
- 🏷️
stacks-sbtc/sbtc:blocklist-client-v1.4.1 - 🔒
sha256:7d865a68c951b69a88646e6db1844e993fd5a74ef15636e58f63af2aec3eca16
📙 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: add withdrawal e2e test by @matteojug in #1979
- feat: scope bitcoin signing decisions to the chain tip by @djordon-stacks in #2152
Full Changelog: v1.4.0...v1.4.1