OQ — S20 · For protocol teams
Every partner, market maker and analyst who asks your team for a CSV is a distraction. Publish your IDL, get typed tables, and let them answer their own questions.
The input is the interface definition you already publish.
Every event and call
One table per event and per instruction, with verified account aliases where the IDL and live schema agree.
Ecosystem visibility
Analysts building Solana-wide dashboards find your program because it is in the catalog.
You keep the IDL
Update the interface definition and the tables follow. Nothing proprietary to maintain.
Send the IDL
The interface definition your program already publishes.
Tables generated
One per event, one per instruction, named consistently with every other program.
Backfill and follow
Historical decode plus continuous decoding at the chain tip.
Live in the catalog
Your dataset page goes up and anyone can query it.
Our program emits no events. Is that a problem?
No. Sixteen of the currently bundled programs are the same. Their data is read from instruction tables, which capture the call and the accounts it touched.
How long does it take?
Usually about a week from receiving the IDL to the dataset page going live, depending on how much history needs backfilling.
Can we see what people query?
Not by default — we do not expose per-user query logs to third parties. Aggregate interest in your dataset is something we are happy to share.
Free for public programs, usually live within a week.