Stats and receipts
What the /stats page shows, how each figure is derived from finalized on-chain evidence, and how ledger figures differ from wallet balances.
What /stats shows
/stats is gitpad's public protocol dashboard. Choose 24h, 7d, 30d or All time for activity figures.
| Metric | Definition |
|---|---|
| Paid to builders | Settled builder fee payouts in the period |
| Earned by builders | Builder fee credits indexed in the period, including fees already paid |
| Trading volume | SOL in for buys and SOL out for sells on the curve, plus verified DAMM v2 trades |
| Live markets | Canonical markets whose launch is confirmed, finalized and indexed |
| Graduated markets | Canonical markets with verified migration evidence |
| Platform fees claimed | gitpad's settled platform fee claims |
| Buyback reserve | Buyback allocations minus verified buyback spending |
| Available liquidity reserve | Liquidity allocations minus open commitments and settled deployments |
| Allocated to treasury | Cumulative treasury allocations |
| SOL bought back | Total of verified buyback receipts, including trading fees |
The page also lists recent completed builder payouts, with repository, amount, settlement time and a link to the transaction.
How figures are derived
- Only finalized evidence counts. Launches, trades, fees and payouts are indexed from finalized Solana transactions that match a market's canonical mint and pool.
- Pending is excluded. Pending payouts, unindexed launches, wrong-pool events, liquidity deposits and migration transfers are not counted.
- Nothing is counted twice. The launch's initial buy is counted once, through its swap.
- Amounts are exact. All accounting is in integer lamports. Expand View data for lamport-precise values.
- One snapshot. All figures on the page come from a single consistent, read-only database snapshot.
Discovery payouts and builder token allocations are separate from builder fee payouts.
Time and currency
- 24h, 7d and 30d are rolling periods ending when the page is read.
- The 24h chart uses hourly UTC buckets; other charts use daily UTC buckets. The All time chart shows the latest 14 UTC days.
- Periods with no activity show as empty. Missing data is never filled with invented values.
- USD values use the current SOL price, not the price on the day of each trade. If no price is available, SOL is still shown.
- Fee charts use the time a fee was indexed, which can differ from the time of the underlying trade.
- Platform reserves and market counts are always all-time.
Ledger figures and wallet balances
The reserve cards describe gitpad's ledger: what has been allocated and spent according to verified records. They are not live wallet balances.
To connect the two, the page separately reads the balance of gitpad's recorded receiving wallet from two independent finalized mainnet RPC reads and compares it with the outstanding reserves:
| Result | Meaning |
|---|---|
| Check passes | The wallet holds at least the outstanding buyback, liquidity and unallocated amounts |
| Reserve balances need reconciliation | The wallet holds less than the ledger says is outstanding |
| Not verified | The RPC reads failed, disagreed, came from the wrong network or drifted too far apart |
Historical treasury allocations are not an outstanding obligation, so they are not part of this check.
Reconciliation
Before any reserve figure is shown, gitpad reconciles its platform revenue and liquidity ledgers against on-chain evidence. If they do not match, the page shows Being verified and hides those totals instead of showing numbers it cannot back.
For builder fees, reconciliation compares indexed earnings, settled payouts and the current on-chain fee balances. A contradiction produces a review state. Balances are never edited to force a match.
Receipts
Every settled payout and buyback on the page links to its Solana transaction. A payout is shown as settled only after gitpad verifies the finalized transaction and the exact amount received by the bound wallet. Share cards for payouts recheck the finalized receipt before they are generated.
Freshness
The update time on the page is when it was read, not proof that every latest transaction has been indexed. Values can lag the chain briefly. A failed read shows as unavailable, never as zero.
Found something wrong? Edit this page on GitHub.