Protocol intelligence
One system at a time: what it is, where it runs, what can be proven.
Gnosis Pay Safe Card Protocol
DRAFTNo published research note describes this system in prose. What follows is the registration and what has been observed against it.
Usage snapshot
How much this payment system is used
Why
Amounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.Why
Amounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.Why
The previous equal window has a zero baseline, so a ratio would be undefined rather than large.Why
Amounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.Why
This window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.Why
This window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.Why
This window is not in the rolling-window catalog, so no method produces a figure for it. Waiting does not change that — the capability has to be built.Why
Amounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.What changed
Deterministic changes only — no cause is inferred
- Payment count · Latest complete day
- ▼ -21.4% compared with the previous equal window, through 2026-09-06 UTC
- Payment count · 7D
- ▼ -3.3% compared with the previous equal window, through 2026-09-06 UTC
industry_signals
Registry and facts read through 2026-09-07 08:14 UTC
Usage trend
Only metrics with a published definition
943per day, low to high6,438
C09 groups post_auth_funds_action_count by protocol; this line is this system's own daily series — 19 published windows at this revision.
633per day, low to high2,379
C09 groups active_payment_address_count by protocol; this line is this system's own daily series — 19 published windows at this revision.
The lines here come from published metric series. Gnosis Pay Safe Card Protocol's 17 capability assessment rows are a separate kind of evidence and are not among them.
Usage programme
Measures this surface will carry, and what each is waiting for
Why
Amount quantiles are not published. They need a per-denomination distribution this system does not compute yet.Why
Amount quantiles are not published. They need a per-denomination distribution this system does not compute yet.Why
The account attribution this measure is derived from has not been published yet, so there is no population to describe.Why
The account attribution this measure is derived from has not been published yet, so there is no population to describe.Why
The account attribution this measure is derived from has not been published yet, so there is no population to describe.Why
No signals engine has run here. The rules are frozen, but their gate is a blind evaluation that has not been performed, and a signal shown before that gate would be a claim this system cannot support.Among SpendGraph-tracked cards
A comparison across the tracked set — not a market ranking
No figure is published for this system yet.
No figure is published for this system yet.
Amounts are published per denomination. Adding them would need a rate SpendGraph does not observe, so there is no single total.
Evidence coverage
17 assessment rows over 17 functions iRows, not functions: a pack that splits one function into two aspects contributes two rows and one function.
Publication coverage
Which blocks the figures above rest on
| Deployment | Chain | Activity | Batches | Blocks | Contiguous | Republished | Data through |
|---|---|---|---|---|---|---|---|
| gnosis-pay-gnosis | 100 | Active | 7823 | 47,817,934 – 48,124,564 | 48,124,564 | 4iCommitted batches whose block range overlaps another — a repair republished the range. Facts are not double-counted; batch fact counts would be, which is why this terminal publishes no fact total. | 2026-09-07 08:14 UTC |
Deployment-wide metrics are on the Overview page at revision metric-v4.iThe registry describes each system separately; C09 computes over the facts the deployment holds. The first can be split per system and the second cannot.
Payment system anatomy
How Gnosis Pay Safe Card Protocol completes a payment
- F01fact
- F02fact
- F03inference
- F04disproven
- F05fact
- F06fact
- +3 more on Functions
- F07fact
- F10disproven
- F11fact
- +3 more on Functions
Architecture overview
System architecture and how value moves through it
Runs on one chain · Constrains what the account may spend · profile arch-gnosis-pay-v5 · revision 1iEvery value in the lanes is a registry declaration bound to evidence, at the protocol version named in the header. Nothing here is inferred from activity.
Multi-chain presence
Where this system runs
Activity, events and amount by chain
Funding mix, by declared share
- DIRECT_
ONCHAIN_ 83.0%TRANSFER / PREFUNDED · external_ inbound - DIRECT_
ONCHAIN_ 8.1%TRANSFER / PREFUNDED · hold_ return - OFFCHAIN_
FUNDING / PREFUNDED · 7.1%emoney_ mint - DIRECT_
ONCHAIN_ 1.8%TRANSFER / PREFUNDED · account_ to_ account
Basis: declared share of funding, in basis points of 10,000. Not a measured amount, and not a share of any market.
Key facts
- System id
- gnosis-
pay - Registry
- gnosis-
pay · 0.2.0 - Registration
- DRAFT
- Programme
- gnosis-
pay - Account model
- SMART_
ACCOUNT_ ADDRESS - Custody
- RESTRICTED_
SELF_ CUSTODY_ SMART_ ACCOUNT - Settlement locus
- CARD_
NETWORK - Networks
- gnosis-
mainnet - Deployments
- gnosis-
pay- gnosis - Issuer / operator
- not declared
- Reserve transparency
- not declared
- Regulatory status
- not declared
- Smart contract upgradeability
- not declared
The rows marked not declared have no field in any registration pack. C01 asserts a legal entity only where the chain record establishes one, and for these systems it does not.
Methodology
- Every count here 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 on this site.
- 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.
On-chain evidence preview
The shape of the evidence behind every figure on this page
| Time | Chain | Event type | From | To | Amount | Tx hash |
|---|
7823 committed publication batches across 1 deployment records — the block ranges are in Publication coverage below.
Related systems
Declared dependencies
Rails this system settles or funds through, as the registry declares them. A graph across registered systems is not published, so none is drawn.