Use case
Protocol analytics
A read model of public chain data. It is not a rating, a yield, or a new protocol.
A team wants to query events, balances, or validator sets without running ad-hoc scripts.
When shared machinery earns a place
Indexing public data is ordinary software. A chain of your own is not required.
When it does not
If the question is about your own customers, use your database. Do not mirror personal data into a public subgraph.
Conventional-first
Indexer, warehouse, access control, a stated finality lag.
You operate the pipeline.
Hybrid
The same pipeline, plus a signed report or a hash of a defined extract.
The hash does not make the methodology true.
On-chain-native
Not generated. Analytics does not need a new asset.
Refused as a default.
Patterns
Components
- PonderGreen — compatible use if you keep the notices
- Graph NodeGreen — compatible use if you keep the notices
- viemGreen — compatible use if you keep the notices
- RethGreen — compatible use if you keep the notices
Questions a person still has to answer
- Which chains, and what is your finality rule?
- Are you joining chain data to personal data?