- # Who staked the 505.1 BTC in PoX-5 bond period 2 — itemized to the sat
-
- **Snapshot:** Stacks block height **9143401** (burn height 970415).
-
- **Call:** `get-total-sbtc-staked-for-bond(u2)` on `SP000000000000000000002Q6VF78.pox-5`
- → `0x0100000000000000000000000bc2a16f80` = **50,510,000,000 sats (505.1 BTC)**
-
- Reproduce (re-runnable):
-
- ```
- curl -s -X POST "https://api.mainnet.hiro.so/v2/contracts/call-read/SP000000000000000000002Q6VF78/pox-5/get-total-sbtc-staked-for-bond?tip=9143401" \
- -H 'Content-Type: application/json' \
- -d '{"sender":"SP000000000000000000002Q6VF78","arguments":["0x0100000000000000000000000000000002"]}'
- ```
-
- ## Stakers — amounts sum exactly to the total
-
- | staker principal | amount staked (sats) | lock | Stacks txid |
- |---|---|---|---|
- | SP2TC7YMDH77T5GP41W6JZK3Q7AJ10ZJ36ZQNGQ79 | 10000000 | L1 | 0x6a2571f18a57c806e4a463f569fa9a24f1fba6b3a8b0d44e2480629eaa15b5c6 |
- | SP8HK160YD5GHXP69VGA0TC7AQJ1X4CDW3XVERSE.sbtc-bond-staker-v1-2 | 2200000000 | L2 | 0xebcd026a802bca6064b6e5b544ce49d84787ea5a9d7776bc45e302b6006bf3a3 |
- | SP4SZE494VC2YC5JYG7AYFQ44F5Q4PYV7DVMDPBG.stbtc-staker-bond-2-v2 | 48300000000 | L2 | 0xd5073db36fdacac07394005df2e76461b145dd4c391f882e1d7e499bebd4f251 |
- | **TOTAL** | **50510000000** | | |
-
- Every row is a `register-for-bond` call with `bond-index u2`. All three Stacks txs are `success`.
-
- Row detail:
- - **Row 1** — L1 lock, burn 970357, BTC lockup tx `0x6fc0c08830c3e3a79e89a9102de0fff83a222bbf231bad18d3715cb88847e27c`, amount-ustx u1336920000.
- - **Row 2** — L2 sBTC, burn 970353, amount-ustx u294122400045.
- - **Row 3** — L2 sBTC, burn 970278, amount-ustx u6457323600000.
-
- ## Method
-
- `protocol-bonds-total-staked` is only ever *increased* by `register-for-bond`. I listed the pox-5 contract's print events
- (`GET /extended/v1/contract/SP000000000000000000002Q6VF78.pox-5/events`, paged, throttled) and kept prints containing
- `(bond-index u2)` and `(topic "register-for-bond")`. Each such print carries `staker` and `sats-total`. The results are exactly
- 3 prints, and they sum to the current map value to the sat (50,510,000,000), so no registration is missing and no partial
- unstake has reduced the total. Every attributed amount matches the `sats-total` field in the tx's own pox-5 print event.