How these numbers are made
Nothing on this site comes from our own database of claims. The indexer reads Solana transactions and accounts, and anyone can recompute every figure from the same data. Where a feature has not shipped, the site says not shipped. It never shows a zero in its place.
Sources
- heads_down program events
- All ten events of interface v1.1: RigRegistered, RigClosed, SeekerVerified, ShiftArmed, HeartbeatsRecorded, RigDug, RigSkipped, ShiftBroken, ShiftEnded and ShiftEndedV2, logged by program HDn4vgLWFLLdexKEwfZwRHjWtizNvdqFteLbMsE67F9p. They are counted only when that program wrote them, only from successful transactions, and only at finalized commitment. Ending a shift logs both ShiftEnded and ShiftEndedV2; the shift is counted once.
- heads_down instruction data
- The heartbeat entries inside dig and record_heartbeats instructions say which ORE round the phone signed for and how many rounds of lease it asked for. Replaying the program's own lease rules over them tells which rounds were dark, and the result must equal the count the program logged when the shift ended.
- ORE's own DeployEvents
- Every Heads Down dig makes ORE emit a DeployEvent whose signer is the Heads Down Executor PDA By3vJvQUsCLexnv7VqHuEhtZZCmpmjZjfhxvqCnWPkge (seeds ["executor"]). Only the heads_down program can sign for it, so ORE can measure Heads Down usage from its own logs.
- Accounts
- Rig, SeekerSeat and ShiftLog accounts. Each one's address is re-derived from its contents (canonical bump) and its owner is checked, so no other account can pass as a rig. Seeker tier means the program itself verified a Seeker Genesis Token in the same transaction.
- ORE rounds
- ORE's ResetEvent for each round (winning square, top miner, Motherlode, total_miners), from api.ore.com or found on chain, stored with its reset transaction signature; a sample is re-read from the chain on every poll. Also the ORE Round account of every round Heads Down dug, read after the round was reset: it is the only place ORE keeps each square's total, which its own arithmetic divides by.
- Market price (morning haul only)
- The one figure that is not on chain: a quote for ORE in SOL from a public price API. It is always shown with the name of its source, and left empty when no source answers.
Definitions
- Rigs
- Rigs registered minus rigs closed, from RigRegistered and RigClosed events. The count is cross-checked against the Rig accounts that exist now, and the overview says whether the two agree.
- Night
- Noon to noon in one fixed time zone (WAT by default). A rig's own time zone is never collected.
- Active rig
- Armed a shift, dug, or ended a shift with at least one dark round that night.
- Retention D1 / D7 / D14
- A cohort is the night of a rig's first armed shift. Dk is the share of the cohort active exactly k nights later. A cell appears only once that night is complete.
- Dark round
- An ORE round covered by a heartbeat lease: the phone, face-down, signed a fresh heartbeat with its Keystore key, and the program accepted it on chain for that round and at most two more. A round with no lease is not dark, whatever the phone was doing.
- Dark hours
- Dark rounds from ShiftEnded events × the measured median ORE round length.
- SOL deployed
- SOL placed into ORE squares by digs, cross-checked against ORE's DeployEvents. It stays in ORE's custody and returns to the rig owner under ORE's rules.
- ORE mined
- ORE credited by ORE's checkpoint rules for each Heads Down deploy, from that round's outcome: a pro-rata share on split rounds, all of it on a solo round won, plus any Motherlode share. It is unrefined, before ORE's 10% refining fee on claim.
- ORE bought / buried
- Not shipped yet (clock-out buy leg, Bury auction). Shown as placeholders.
- Share of ORE miners
- Per round: distinct Heads Down wallets that deployed ÷ ORE's total miners for that round.
- Gate-open rate
- Digs ÷ (digs + on-chain cost-gate refusals). The crank only submits when it expects the gate to open, so this rate runs high. It is shown next to the share of dark rounds that were dug.
Skips
When the program declines to dig for a rig it logs a RigSkipped event with a precise code, and the transaction still succeeds for the other rigs in it. A skip places no SOL on any square. The Skips page counts them by code and words each one as what happened on chain:
- CostGate
- The price gate was closed: mining cost more than the rig's plan allows, so the program did not dig.
- StaleHeartbeat
- A replay was rejected: the heartbeat's counter was not newer than the last one the program accepted.
- LeaseExpired
- The phone went quiet: no heartbeat lease covers this round, so the program refused to dig.
- RigNotArmed
- No active shift: the rig is idle, broken, or cooling after a pickup without a fresh heartbeat.
- Signature checks
- Codes in the 0x2560_00xx range come from the P-256 heartbeat check (wrong key, wrong message, malformed signature) and codes in 0x5347_00xx from the Seeker Genesis Token check. They are shown with their own names, never folded into a generic error.
The morning haul
The haul of one finished shift is the same summary the phone shows at clock-out. It is served only once ORE has reset every round the shift dug, so its on-chain figures do not change afterwards.
- Rounds
- Every ORE round from the shift's first to its last: whether it was dark, which squares were dug, and which square ORE drew.
- SOL placed, fees
- SOL placed is the sum of the digs' RigDug amounts. Fees are what the shift spent beyond that: the per-dig Automation fee, which goes to the Heads Down Executor and reimburses the crank that sent the dig. The wallet's own transaction fees for clocking in and out are not included.
- Effective price
- (SOL placed − SOL that ORE returns + fees) ÷ ORE mined, for this shift only. Empty when the shift mined no ORE. SOL returned follows ORE's per-square fee formula and is exact when the Round account was read.
- Market price
- The labelled quote described under Sources, for comparison. Mining can cost more or less than buying; the haul shows which it was.
- Streak
- The program's own streak rule replayed over the rig's ended shifts: a shift counts when it completed with at least one dark round.
What is not shown, and why
- Rigs by region. The app collects no location, and no opt-in region data exists yet, so there is no region view. Milestone time windows are time zones, not places.
- Returns. Heads Down is a way to accumulate ORE by the cheaper route when the on-chain gate says mining costs less than buying. It is not a return on capital, and this site never presents it as one.
- First pickup time. The chain cannot see when a phone was picked up after a shift ended, so the haul leaves it empty. Only the phone knows.
Simulated data
A demo can run against the indexer's deterministic simulator instead of the chain. Its API then marks every response simulated: true, and this site then shows a striped SIMULATED banner and a SIM badge on every tile, and links no explorer. A site build pinned to one dataset refuses responses from any other. The API reference is in the footer. Back to the overview.