OQ — F00 · For protocols
OnchainQueries decodes from the IDL you already publish. Give us the interface definition and every event and instruction becomes a typed table that anyone can query — which means analysts stop asking your team for CSVs.
- Programs indexed
- 37
- Tables generated
- 1,074
- Input needed
- 1 IDL
- Cost to you
- $0
No custom indexer, no subgraph to maintain, no schema for you to design.
Send the IDL
The Codama or Anchor interface definition your program already publishes. That is the whole input.
We generate the tables
One table per event and one per instruction, named with the same convention as every other program in the catalog, with verified account aliases where the IDL and live schema agree.
Backfill and follow
Historical decode plus continuous decoding at the chain tip, with a high-watermark slot recorded on every query that reads it.
It appears in the catalog
Your protocol gets a dataset page listing every table, both name forms and an example query — and anyone can start answering questions about it.
What does it cost us?
Nothing. Getting a program decoded into the public catalog is free — it makes the platform more useful, which is the point. Private or pre-launch decoding is an enterprise arrangement.
What if our program has no events?
That is common — sixteen of the currently bundled programs declare no events at all. Their activity is read from instruction tables instead, which capture the call and the accounts it touched. Nothing is lost, the queries just look different.
Do we have to maintain anything?
Only the IDL, which you maintain anyway. Send an updated one when the program changes and the tables follow.
Can we keep it private before launch?
Yes, under an enterprise arrangement — private tables resolved through the same catalog validation, visible only to your organisation.
Will you index a fork of our program?
If it publishes an IDL, technically yes. We will talk to you first if it is likely to be confused with yours.
Free for public programs. Usually live within a week.