SpendGraphTERMINAL INTELLIGENCE no index 2/4 publishing 2 chains 2026-09-01 06:40 UTC 27% fact 17% inference 14% private 中文

Protocol intelligence

One system at a time: what it is, where it runs, what can be proven.

Ether.fi Cash (cash-v3)17/17 Gnosis Pay Safe Card Protocol17/17 RedotPay17/17 UR Account / Card Protocol17/17

Ether.fi Cash (cash-v3)

DRAFT

No published research note describes this system in prose. What follows is the registration and what has been observed against it.

Registryetherfi-cash · 0.1.0 System idetherfi-cash Programmeetherfi-cash Versionetherfi-cash-v3-optimism
Observed activityAmount aggregation
Not observedAmounts are published per denomination; a single figure would need a rate SpendGraph does not observe.
Payment eventsC06 · C09
Not yet publishedNo payment-event count is published for this system yet.
Active payment addressesAddress attribution
—
Connected chainsC01 deployment model
14
0 carrying published facts
First observedC06 publication
Not yet publishedNo committed publication batch yet.

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 Ether.fi Cash (cash-v3) completes a payment

Native Integrated Dependent Not observed iWhere a function happens and whether it can be seen. Not a grade, not a ranking, and not ordered best to worst.
Identity
Who is involved
Not observed Not in catalogiThe frozen function catalog defines no function for this group, so no assessment can exist. Not a gap in this protocol's registration.
Account
Where value is held
Native
1/1
1 fact
Key evidence
  • F01fact
Funding
How value enters
Integrated ×2
2/2
1 fact 1 inference
Key evidence
  • F02fact
  • F03inference
Authorization
How payments are approved
Native Dependent ×5
6/6
5 disproven 1 fact
Key evidence
  • F04disproven
  • F05disproven
  • F06fact
  • +3 more on Functions
Settlement
How value moves
Native ×4 Dependent ×4
6/6
4 fact 4 disproven
Key evidence
  • F07fact
  • F10disproven
  • F11fact
  • +3 more on Functions
Credit
How credit is provided
Not observed Not in catalogiThe frozen function catalog defines no function for this group, so no assessment can exist. Not a gap in this protocol's registration.

Architecture overview

System architecture and how value moves through it

Account
Who participates, and what the account is
SMART_ACCOUNT_ADDRESS
Account identity survives an address change
Custody
RESTRICTED_SELF_CUSTODY_SMART_ACCOUNT
Funding
How value enters, and how a balance is held
DIRECT_ONCHAIN_TRANSFER / PREFUNDED
COLLATERALIZED_CREDIT / CREDIT
BRIDGED_TRANSFER / PREFUNDED
Balance
SMART_ACCOUNT_ASSET_BALANCE
Settlement
Where the obligation settles
SHARED_POOL · the four settlement dispatchers
OFFCHAIN_PROCESSOR · after the bridge
Rails
etherfi-reap etherfi-rain etherfi-pix etherfi-cardorder

One primary chain, funded from others · Decides each payment · profile etherfi-cash-arch-optimism · 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

optimismPrimaryno facts yet
scrollHistoricalno facts yet
ethereumFundingno facts yet
baseFundingno facts yet
arbitrumFundingno facts yet
bscFundingno facts yet
hyperevmFundingno facts yet
polygonAccount onlyno facts yet
sonicAccount onlyno facts yet
mantleAccount onlyno facts yet
avalancheAccount onlyno facts yet
lineaAccount onlyno facts yet
chain-9745Account onlyno facts yet
chain-4217Account onlyno facts yet

Activity, events and amount by chain

Not yet publishedC09 publishes no metric broken down by chain for one system, so there is no per-chain figure to state a basis for.

Funding mix, by declared share

  • DIRECT_ONCHAIN_TRANSFER / PREFUNDED · Debit mode
  • COLLATERALIZED_CREDIT / CREDIT · Credit mode

Basis: declared share of funding, in basis points of 10,000. Not a measured amount, and not a share of any market.

1 further declared funding profile carries no share, so it is absent from the ring rather than zero.

Activity & adoption analytics

Only metrics with a published definition

Not applicableActivity has no published metric definition. The tab is kept because the module is part of the design; a series would have to be invented.
Not yet publishedC09 has published no post_auth_funds_action_count series for this system at this revision.
Not yet publishedC09 has published no active_payment_address_count series for this system at this revision.
Not applicableFlows has no published metric definition. The tab is kept because the module is part of the design; a series would have to be invented.
Not applicableVelocity has no published metric definition. The tab is kept because the module is part of the design; a series would have to be invented.
Not applicableRetention has no published metric definition. The tab is kept because the module is part of the design; a series would have to be invented.
Not applicableUse cases has no published metric definition. The tab is kept because the module is part of the design; a series would have to be invented.

Ether.fi Cash (cash-v3) carries 19 assessment rows; none of them is a time series.

On-chain evidence preview

The shape of the evidence behind every figure on this page

Time Chain Event type From To Amount Tx hash
Not observedThis surface reads only what C10 publishes, and a raw event is a domain record C10 does not publish. The From and To columns would also name addresses, which this site does not disclose for any system.

0 committed publication batches across 2 deployment records — the block ranges are in Publication coverage below.

Related systems

Declared dependencies

etherfi-reapRail
etherfi-rainRail
etherfi-pixRail
etherfi-cardorderRail

Rails this system settles or funds through, as the registry declares them. A graph across registered systems is not published, so none is drawn.

Publication coverage

Which blocks the figures above rest on

DeploymentChainActivityBatchesBlocksContiguousRepublishedData through
etherfi-cash-optimism10Active0——0—
etherfi-cash-scroll534352Dormant0——0—

Evidence coverage

disproven10
fact7
inference2

19 assessment rows over 17 functions iRows, not functions: a pack that splits one function into two aspects contributes two rows and one function.

Key facts

System id
etherfi-cash
Registry
etherfi-cash · 0.1.0
Registration
DRAFT
Programme
etherfi-cash
Account model
SMART_ACCOUNT_ADDRESS
Custody
RESTRICTED_SELF_CUSTODY_SMART_ACCOUNT
Settlement locus
SHARED_POOL
Networks
optimism, scroll, ethereum, base, arbitrum, bsc, hyperevm, polygon, sonic, mantle, avalanche, linea, chain-9745, chain-4217
Deployments
etherfi-cash-optimism, etherfi-cash-scroll
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.

Recent signals

Changes and events

Not applicableno signals engine exists; the design's signal feed has no component behind it yet

industry_signals

Registry and facts read through 2026-09-01 06:40 UTC

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.