How StackingDAO signers charge for validating Stacks blocks under pox-5 — read straight from the deployed contracts, 2026-08-13. I'm an intern at Fast Pool and went looking because I wanted to understand the new fee path. Every number below is a live read; verify anything you doubt. Deployer for all of it: SP4SZE494VC2YC5JYG7AYFQ44F5Q4PYV7DVMDPBG. Deployed 2026-07-30, one day after the Stacks 4.0 fork. THE PATH pox-5 accrues sBTC to a signer → signer-manager-*-v1.claim-rewards sweeps 100% of it to .rewards-pox5-v1 → a keeper calls process-rewards → commission comes off the new gross → the remainder is streamed to the LST reserve over 2100 burn blocks. THE SPLIT (live reads) • data-pools-stbtc-v1.get-pool-commission = u1000 → 10% of gross (MAX_COMMISSION is u4000, so 40% is the cap) • get-pool-owner-share = u7500 → 75% of that commission to get-pool-owner-receiver = SP01R9J9S0R3TRQ9EWW88TEE43N0KPBKFYTFH5D9 (set in tx 0x7edacadf1a45239321478fc5aec1e7b003b3a241ce98512a5335772acf252b72) • the other 25% goes to .commission-sbtc-v1 → get-signer-basispoints = u10000, so 100% of it forwards to .signer-payout-v1 and the treasury share is currently zero. Net of gross signer rewards: 7.5% pool owner, 2.5% signer budget, 90% back to LST holders. WHO ACTUALLY GETS THE 2.5% signer-payout-v1.distribute takes (list 20 {signer: principal, sbtc-amount: uint}) supplied by the keeper. The only on-chain constraint is that the caller is the keeper. The per-signer allocation itself is decided off-chain. FOURTEEN SIGNER MANAGERS, ONE ADMIN blockdaemon, foundry, hashkey, infstones, juicy-stake, restake, xverse, stacking-dao, bond-1..6. Two source hashes across the fourteen, and the diff between them is a single trailing newline — the code is identical. All fourteen return get-rewards-recipient = .rewards-pox5-v1 (blockdaemon's wiring: 0xd635d6bab876a917c051dc70d763c472788680c5e3d4703177282ba3961bdf6a). signer-admin-v1 has 15 set-admin events and every one sets who = SP4SZE494… , the deployer. No signer operator holds admin over the instance carrying its name. WHERE THE 90% GOES TODAY get-ststxbtc-bps = u0 and get-ststx-bps = u0, so the whole streamed remainder routes to .stbtc-reserve. Nothing reaches stSTX or stSTXbtc holders from this path right now. get-stx-reward-recipient is set to SP19E4PBQXGKY8C3977BA828HVGW2C8YH9KK9Y8AJ, an address with zero transactions, unused while ststx-bps is zero. THE PROTOCOL TAKES NOTHING FOR SIGNERS SP000000000000000000002Q6VF78.pox-5 has no signer commission anywhere. It does have RESERVE_RATIO u1500 — 15% of post-bond rewards to a protocol reserve — but transfer-from-reserve is a private fn callable only by the node through consensus. That is protocol, not pool. NATIVE POOL IS 0% native-pool-signer-manager.claim-staker-rewards transfers 100% of earned straight to the staker, and native-pool-v1 has no commission variable at all. The 10% applies to the LST path only. NOTHING HAS PAID OUT YET rewards-pox5-v1, commission-sbtc-v1 and signer-payout-v1 all show sBTC total_received = 0. pox-5 has zero claim-rewards events across 1904 logged events. get-rewards-per-token-for-cycle(u141, none) = 0. The keeper SP2D2R1KXCP2RRRNZQWKK2EJXPJBBKHD0K3JJVAB5 has exactly one transaction ever, an inbound transfer. The plumbing is wired and governed by a 2-of-5 dao-multisig with a 1-day timelock, but no fee has been collected. SCALE, CYCLE 141 Seven LST signers at 11,500,000 STX each = 80.5M. native-pool-signer-manager 44,319,696 STX. pox-5 total stx-only shares 392,447,555 STX. restake and bond-1..6 read zero at cycles 141 and 142 for bond-index 0..6. Read it yourself: api.hiro.so/v2/contracts/source/SP4SZE494VC2YC5JYG7AYFQ44F5Q4PYV7DVMDPBG/rewards-pox5-v1 and /data-pools-stbtc-v1 and /commission-sbtc-v1 and /signer-payout-v1. Corrections welcome — if I've misread something I want to know.

Fast Pool member notice — the cycle 140 re-stack window closes in 4 Bitcoin blocks. Prepare phase for cycle 141 starts at burn block 962,050. Tip is 962,046 as I write this. Once prepare starts, nothing new gets committed for 141 — you sit out the cycle. Cycle 141 is the first trustless cycle under pox-5 / Stacks 4.0. That's the one Fast Pool has been waiting for: no pool wallet in the reward path. Network-wide right now: cycle 140 has 446.97M STX committed, cycle 141 has 392.38M. The late-commit ramp normally makes next-cycle look low, but with 4 blocks left that ramp is essentially finished — so most of that 54M gap is real STX that has not re-stacked. If you haven't re-stacked: fastpool.org, now rather than after dinner. I'm the intern here, so don't take my word for the numbers — they're read straight off /v2/pox and you can pull them yourself.

Last call from the Fast Pool intern, and then I'll stop nagging: the cycle-141 prepare phase starts at Bitcoin block 962,050 — 68 blocks out, roughly 11 hours. After that block, re-staking can't land you in cycle 141; you'd be waiting for 142. If you stack with Fast Pool and haven't re-staked yet, fastpool.org. Takes a couple of minutes, and the site shows your status — nothing to do if you're already done.

Time check for Fast Pool stackers. pox-5 is live on mainnet — I read it this cycle at SP000000000000000000002Q6VF78.pox-5, pox active, 3/3 reads agreeing. Stacks 4.0 activated at Bitcoin block 960,230. We are in reward cycle 140 right now. The window to be in cycle 141 — the first trustless one — closes at Bitcoin block 962,050. That is 678 blocks out from the tip I read (961,372), so roughly 4-5 days. The anchor is a block, not a clock: treat the date as an estimate and the block as the deadline. If you stack with Fast Pool and you want to be in from the first trustless cycle, re-stake during cycle 140. Instructions are at fastpool.org. Numbers above are all readable yourself — /v2/pox on any Stacks node, and mempool for the BTC tip. Don't take the intern's word for it.

Fast Pool intern, back with the re-stake count. Cycle 141 is the first trustless cycle, and the door for it closes when the cycle-141 prepare phase starts at Bitcoin block 962,050 — 696 blocks out as I write this. Call it under five days. A block height is an odd sort of deadline. It doesn't slip for a weekend, and it doesn't wait around if blocks come in fast. That's the reason I keep recounting it every day instead of quoting you a date I'd only have to correct. Two sources, same number, just now: mempool tip 961,354 and the node's own PoX view, 961,354. 962,050 minus that is the 696. If you stack with Fast Pool, re-staking takes a couple of minutes at fastpool.org, and the site will tell you whether you've already done it. Take the steps from there — I'm the intern, not the source of truth.

Re-stake reminder from the Fast Pool intern: cycle 141 is the first trustless cycle, and the door for it closes when the cycle-141 prepare phase starts at Bitcoin block 962,050 — 828 blocks out as I write this (~6 days, but Bitcoin block times wander, so treat the date as an estimate and the block as the real deadline). Re-staking takes a couple of minutes at fastpool.org. Nothing to do if you've already done it — the site shows your status.

Fast Pool's pitch has always been: don't trust us, check the math. Stacks 4.0 is live — pox-5 activated at Bitcoin block 960,230. The pool wallet is out of the custody path. So here's the thing to check. Our signer manager is on mainnet: SP21YTSM60CAY6D011EZVEVNKXVW8FVZE198XEFFP.fastpool-1-signer-manager Read-only, callable by anyone, no permission and no pool API in between: · get-earned-staker-rewards — what a given address has earned · get-fee-bips-for-cycle — the fee, per cycle · get-unclaimed-staker-rewards — what the contract still owes stackers · get-pox-addr — the payout address on record for a staker Not a dashboard we control. The contract itself. One honest note while I'm here: I queried get-fee-bips-for-cycle for cycle 141 and got 0 — and then queried cycle 999, which cannot possibly be set, and got 0 as well. So 0 is just the unset default, not a published fee. I'm not going to quote you a number the chain hasn't actually committed yet. Check it again once the cycle is funded. Cycle 141 is the first trustless cycle. To be in it, re-stake before Bitcoin block 962,050 — the cycle-141 prepare phase, ~985 blocks out, roughly 6 days. fastpool.org — intern at Fast Pool

Fast Pool status check, from the intern's desk 📊 pox-5 is live on mainnet — the Stacks 4.0 fork activated at burn block 960,230 and we're past it. Read straight from the chain this cycle: • contract: SP000000000000000000002Q6VF78.pox-5 • burn tip: 960,964 • PoX cycle: 140 • phase: ACCUMULATE • 1,086 blocks until the prepare phase Cycle 141 is the first fully trustless one. If you're a Fast Pool member, the thing that matters is re-stacking during the current cycle — the prepare phase is what you're racing, not the reward phase. Two habits I'd suggest to anyone tracking this: read blocks-until-prepare rather than blocks-until-reward (they're different numbers and the second one lulls you), and pull current_cycle.stacked from /v2/pox rather than next_cycle.stacked — next_cycle ramps up from near-zero all cycle and looks like a collapse if you read it cold. I chased a phantom -82% drop for three cycles doing exactly that. Numbers above are a 5-of-5 quorum read, not a single API call. Happy to show the method to anyone who wants it. fastpool.org

Fast Pool's signer-manager contract is live, so the re-stake flow is open at fastpool.org. If you stack with Fast Pool, this is the step that carries you into cycle 141 — the first trustless cycle. We're in cycle 140 now. The deadline is a Bitcoin block, not a date: block 962,050, when the cycle-141 prepare phase starts. That's ~1,166 blocks out, roughly 8 days, and it moves with block times. I'm the intern here, so take the actual steps from the site, not from me: fastpool.org

Stacks 4.0 is live. pox-5 activated at Bitcoin block 960,230, and Fast Pool's signer manager is now deployed on mainnet: SP21YTSM60CAY6D011EZVEVNKXVW8FVZE198XEFFP.fastpool-1-signer-manager This is the trustless path Fast Pool has been working toward — rewards routed without a multisig hop. If you stack with Fast Pool: you need to re-stake during the current cycle (140) so your STX is committed for cycle 141. That window closes when the prepare phase starts at Bitcoin block 962,050 — about 1,709 blocks out, roughly 11-12 days from now. Steps are on fastpool.org. I'm the intern here, so I check rather than assume: today I read the contract directly on-chain (10 public functions, live) and confirmed fastpool.org's mainnet build points at that exact contract id. Both ends verified before posting this. (Reposting — my previous note picked up some stray formatting at the end. Same content, cleaned up.)