More than one set of these contracts exists — the same pool and the same DAO deployed twice, holding different money — so this page reads a list of them and puts them side by side. Every figure below is a variable one of those contracts keeps or a count of the events it printed. There is no APY here, no annualisation, and no average the chain does not itself hold.
{{ failed }}
Nothing on chain registers a deployment and no API answers “which contracts share this source”, so the list is configuration — DEPLOYMENTS in config.ts, extended for a visit with ?deployments=. Each is then asked what functions it actually answers to before it is read, because the same code deployed twice is never quite the same code. Pick one to read in full below.
Several of these calls are permissionless: the mandate is the state on chain, not the caller. A swept deposit still uncredited, a lapsed address still holding somebody's STX, a proposal that carried and was never spent — anyone can finish any of them, and none of them moves a coin of the caller's. {{ workNote }}
Nothing is standing on any bridge that a work list can be built from. Every announcement in reach has been credited, cancelled or released.
Looking at what has left that address…
Not looked at on bitcoin — this page reads the newest few, and older announcements are usually waiting on their own member rather than on a keeper.
The bitcoin side could not be read: {{ w.blind }}
Nothing has been spent out of that address to an sBTC deposit address yet. Until it is, this announcement is only holding the pool's room.
{{ d.why }}
Step 1 was paid for and step 2 never happened. Only the member can reveal one — the salt behind the hash never leaves their browser — but once {{ commitTtl }} have passed anyone may cancel it, which hands the STX leg back to them and frees the room it was holding.
Every number here is one variable of get-pool. The four places principal can sit do not overlap, so they add up; honey is counted apart from it, because it is.
The reads that explain the eight above: the balance itself, and the two ways it can differ from what the books say is owed.
{{ syncNote }}
get-stake-preview computes it, so the page never reproduces the allocation cap, the STX floor or the launch floor in JavaScript. stake is permissionless: the only thing gating a roll is the clock.
{{ epochsNote }}. An epoch is one bond the pool actually committed to. Carried is what fitted against what was eligible; shares is what is still committed, which falls when somebody leaves mid-term; credited against shares is the honey that epoch earned over what it staked — a ratio, not a rate, and deliberately not annualised.
This pool has never staked, so it has no epochs. Its first roll opens epoch 0.
{{ activityNote }}
Bringing L1 bitcoin in is five steps and two of them can be abandoned, so the interesting number is not the volume but the conversion: how many commitments became reveals, and how many reveals became credited positions.
{{ bridgeBlockedNote }}
{{ bridgeLogNote }}
{{ floorNote }}. Executing a proposal that carried is permissionless — the mandate is the vote, not the executor — and a mandate left unspent lapses when its window closes.
{{ floorQuietNote }}
{{ checksNote }}