On-chain evidence
How a conclusion reaches the chain it rests on, and what the current state of that chain of evidence is — including where it is thin.
Evidence chain
How a figure on this site reaches the block it rests on. Each stage names the component that owns it.
C09
Metric
A published series at a pinned catalog revision.
C06
Payment fact
Committed in a publication batch over a block range.
C05
Interpretation
A reading of one transaction against a registered ABI.
C03
Raw record
Log, transaction and receipt, as the chain returned them.
C02
Finalized block
Read at the finalized head, never at the latest.
Publication coverage
Every registered deployment and what C06 has committed for it.
| Deployment | Chain | Activity | Batches | Blocks | Contiguous through | Republished | Data through |
|---|---|---|---|---|---|---|---|
| etherfi-cash-optimism | 10 | Active | 0 | — | — | 0 | — |
| etherfi-cash-scroll | 534352 | Dormant | 0 | — | — | 0 | — |
| gnosis-pay-gnosis | 100 | Active | 188 | 47,817,934 – 47,841,962 | 47,841,962 | 0 | 2026-08-21 16:12 UTC |
| ur-mantle-mainnet | 5000 | Active | 47 | 31,420,289 – 99,600,000 | 47,816,147 | 22 | 2026-08-20 13:57 UTC |
Metric catalog state
Where a metric is not processed at the pinned revision, whether the history exists at an earlier one. This distinguishes 'the stage never ran' from 'the catalog moved and nothing recomputed'.
| Metric | State | Points at pinned revision | History at an earlier revision |
|---|---|---|---|
| Payment events post_auth_funds_action_count | Observed | 3 metric-v4 | none |
| Reversals reversal_count | No data | 0 metric-v4 | 394 points as `authorization_reversed_count` at metric-v3, 2025-06-12 00:00 UTC to 2026-08-19 00:00 UTC |
| Authorization adjustments authorization_adjusted_count | No data | 0 metric-v4 | 76 points as `authorization_adjusted_count` at metric-v3, 2025-07-02 00:00 UTC to 2026-08-08 00:00 UTC |
| Active payment accounts active_account_count | Observed | 1 metric-v4 | 436 points as `active_account_count` at metric-v3, 2025-06-11 00:00 UTC to 2026-08-20 00:00 UTC |
What this terminal does not publish
Stated rather than omitted. An absence a reader has to notice is not a boundary.
| observed_amount_totals | Not observed | Amounts are reported per denomination with no total. A cross-currency figure would need an exchange rate, and SpendGraph does not observe one on-chain. |
|---|---|---|
| industry_signals | Planned | The product design has a signal feed. No component produces one, so there is no panel here rather than an empty panel. |
| protocol_ranking | Not observed | Forbidden by the product specification: capability and coverage are described, systems are not ranked. |
| market_share | Not observed | The observed population is SpendGraph's coverage, not the market. A share would need a denominator nobody here has measured. |
| identity_capability_group | Research required | The frozen function catalog defines no identity function. The registry's identity vocabulary is identity_continuity, which asks a different question: whether an account survives a change of holding address. |
| credit_capability_group | Research required | Credit is carried as a funding model on an assessment row and as rail roles, not as a catalog function. There is nothing for a protocol to be assessed against. |
| entity_directory | Not observed | The public read model carries no account reference at all, so entities are counted and never listed. |
Methodology
- Every count on this site is SpendGraph's observed coverage. It is not a total for the on-chain payment market, and no denominator for that market is published anywhere here.
- Counts are read from C09's published series at a pinned catalog revision. This page performs no count of its own — a second implementation of a published metric is a second thing that can be wrong.
- Publication batches answer how far coverage reaches, never how many facts exist. A repair republishes a range, so summing batch fact counts double-counts the repaired part: on 2026-08-21 that sum was 85,021 against 81,034 actual facts, with zero retractions.
- A registration status describes how far SpendGraph's own review of a pack has got. It is not an assessment of the protocol, and every review state is compatible with a deployment that stopped carrying payments months ago — which is why activity is a separate column.
- The payment function catalog is frozen at seventeen entries. A new protocol term is mapped onto an existing function rather than growing the catalog, so a function absent from a protocol's assessment means nobody has assessed it — not that it does not exist.
- The six capability groups are defined by this site alone, as a presentation over the seventeen. Two of them — Identity and Credit — have no catalog function, so no protocol can be assessed against them and they are shown as such.