Who uses onchain data for finance and BI reporting?

Fintechs that keep their own ledger, consumer finance apps and data analytics providers whose finance and BI teams report on onchain activity.

Goldsky

Onchain data for finance and BI reporting

Talk to our team

What is onchain data for finance and BI reporting?

Onchain data for finance and BI reporting is the full history of your contracts’ activity, decoded into readable columns and kept current in your data warehouse.

Fintechs, consumer apps and data providers need it so finance and BI teams can report on onchain activity with the same tools and joins they use for the rest of the business.

Goldsky can backfill that history, decode every event and keep writing new ones to your warehouse; your team builds the totals, reports and dashboards.

How onchain data reaches finance and BI reports

The diagram follows your contracts’ activity from the first event on the chain to the reports your team builds, and shows who does each step. Your setup may differ.

TurboBackfill historyLoaded first, then kept live

Activity builds upEvery event since your contracts launched

TurboDecode every eventReadable columns for each one

Build your reportsDaily totals joined with your other data

TurboWrite to your warehouseBeside the rest of your data

Goldsky

Let activity build up on the chain
Every event your contracts have emitted since launch is part of the history finance reports on.
Contracts emit events for each transfer, mint, deposit or trade. The chain keeps them in raw encoded form, which reports can’t read until they’re decoded.
Backfill the history
Handled by Goldsky Turbo
Year-to-date and launch-to-date figures need every past event as well as new ones.
Load every event from each contract’s deployment block, then keep the data current. A backfill that starts late leaves the earliest periods short with no sign they’re incomplete.
With Goldsky, a Turbo Pipelines job filtered to your contract addresses backfills history from the data lake and exits when done, and a streaming pipeline carries on from there.
Run a one-time backfill job (opens in a new tab)
Decode every event into columns
Handled by Goldsky Turbo
Analysts need named fields such as sender, amount and token, not encoded bytes.
Decode each event with the contract’s ABI and keep the transaction hash and block with every row, so any number in a report can be traced to the chain. An event left undecoded drops out of every report built on the table.
Turbo Pipelines decodes events in SQL with _gs_log_decode, using an ABI you supply or one fetched from a block explorer.
Decode custom contract events (opens in a new tab)
Write decoded events to your warehouse
Handled by Goldsky Turbo
Finance and BI work where the rest of the company’s data already sits.
Land the rows in a form your warehouse reads, partitioned so queries for one day or chain stay fast. Rows a reorg removes have to come out, or totals include activity that never settled.
Goldsky’s S3 sink writes Parquet files with optional Hive partitioning, which warehouse engines such as Athena, Spark and Trino read directly; append-only files receive reorg corrections as records your load applies.
Write events to S3 as Parquet (opens in a new tab)
Build your reports
The reports finance and BI need are totals and trends, joined with the company’s other data.
Daily volumes, balances and per-customer figures are queries in your warehouse, joined with your own customer and product tables. Keep the definitions in one place, so the same metric doesn’t come out differently in two dashboards.