9.6.0 (2026-10-12)
Release Type: ✅ OPTIONAL
DB Migration: ✅ No
docker pull ghcr.io/hirosystems/stacks-blockchain-api:9.6.0
This feature release extends the v3 staking endpoints with richer bond and PoX cycle schedules:
- Bond schedules now include an
enrollment_cutoffpoint: the first Bitcoin height at which pox-5 rejects new bond registrations (#2713) - Bond and PoX cycle schedule points now carry Bitcoin block times: a confirmed
timefor past blocks and an estimatedprojected_timefor future ones. Points on past Bitcoin blocks with no anchored Stacks block get atimeinterpolated from the nearest anchored blocks (#2717, #2720) - Every timestamp across the v3 API now has a matching
time_iso(ISO 8601) field (#2717) GET /extended/v3/staking/bonds/{index}now returns a bond that hasn't been set up yet with aprojectedstatus and its projected schedule, instead of a404(#2719)
It also includes:
- Every v3 endpoint that takes a transaction id or block hash now redirects (
302) a hash given without the0xprefix to the same URL with the prefix, matching v1 (#2712) - A new
mempool_tx_confirmation_secondsPrometheus histogram, labeled by txtype, that measures how long transactions wait in the mempool before being mined (#2711)
What's Changed
- fix: redirect v3 tx id and block hash params missing the 0x prefix by @rafa-stacks in #2712
- feat: add enrollment_cutoff to the bond schedule by @rafa-stacks in #2713
- feat: add mempool_tx_confirmation_seconds metric by tx type by @rafa-stacks in #2711
- feat: add confirmed/projected Bitcoin block times to schedules and time_iso across v3 by @rafa-stacks in #2717
- feat: project future bonds in /extended/v3/staking/bonds/{index} by @rafa-stacks in #2719
- feat: interpolate Bitcoin block times of past schedule points no Stacks block anchored to by @rafa-stacks in #2720
- chore(release): 9.6.0 [skip ci] by @rafa-stacks in #2721
Full Changelog: v9.5.0...v9.6.0