Version 1.2.0 of the sBTC signer contains a critical update adding support for the upcoming Stacks Core 3.3.0.0.2 release, as well as a number of robustness and performance enhancements.
⚠️ Please ensure that you've upgraded your sBTC signer prior to upgrading your Stacks node to 3.3.0.0.2.
Highlights • Images • Upgrade Instructions • What's Changed
✨ Highlights
✏️ Complete the highlights section with a brief list of notable changes
- Compatibility with Stacks node
3.3.0.0.2 - Bump Rust to
1.91 - Reduced dependencies on
stacks-coreinternal types - Improved handling of Stacks block backfill (reduced memory pressure)
🐳 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.2.0 - 🔒
sha256:4f82dfc07d876138f72a15e8dc4815fc31f847bef6f3ba430a738d524d955a26
Blocklist Client
- 🏷️
stacks-sbtc/sbtc:blocklist-client-v1.2.0 - 🔒
sha256:7a72f695d5563ce5e981c57e39a4148c6ef33448179430f97a352c4c35c962cf
📙 Database migrations
Important
If you run your signer using the --migrate-db flag, database migrations will be applied automatically. If you do not use this flag, you must manually apply the migrations.
--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
- Backup 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
- Update your sBTC images to those specified above
- Restart your sBTC signer and blocklist client
📝 What's Changed
Click to expand
- feat: relaxed handling of v2 pox responses (specifically epochs) by @cylewitruk in #1836
- chore: fix openness local docker postgresql for devenv and ci by @djordon in #1838
- Update attestation workflow by @fabergat in #1839
- feat: use local stacks types by @djordon in #1837
- Update Emily Workflow Triggers by @BowTiedDevOps in #1840
- chore: bump rust to 1.91 by @djordon in #1849
- feat: remove the rng unused parameter from the tx-signer event loop by @djordon in #1848
- feat: consolidate DKG, remove dkg_target_rounds by @matteojug in #1844
- fix: handle testnet stacks blocks backfill by @matteojug in #1850
- fix: add a custom serialize implementation for StacksBlockHash by @djordon in #1842
- Add Emily Sidecar And Cron Pipelines by @BowTiedDevOps in #1843
- fix: Emily correctly respond to get_withdrawals after reorg by @MCJOHN974 in #1809
- [chore]: add machete by @MCJOHN974 in #1852
- feat: reduce memory usage when fetching stacks blocks headers for a tenure by @djordon in #1851
- fix: release builds broken because of carelessly hidden impls by @djordon in #1856
- chore: update stacks core to release 3.3 by @djordon in #1841
- feat: use withdrawal ids table for checking withdrawal requests by @djordon in #1791
- feat: switch from reclaim script to reclaim script hash by @MCJOHN974 in #1723
- chore: restrict fullfillment for non-completed Emily events by @MCJOHN974 in #1781
- feat: use
raw_valuefield for stacks core events by @djordon in #1866 - chore: bump version of stacks core dependencies to 3.3.0.0.1 by @djordon in #1871
- feat: improve stacks blocks backfilling by @djordon in #1857
- fix: testnet backfill with fallback client by @matteojug in #1868
Full Changelog: v1.1.1...v1.2.0