Skip to main content

​
Who it’s for

Teams that need raw onchain events in their own database: protocol teams indexing their own contracts, analytics platforms building chain-wide event feeds, and data teams covering custom or non-standard events that the decoded endpoints don’t model. The output is a complete, ordered, reorg-safe log table you decode against your own ABIs.

​
Raw logs vs decoded recipes

Data Feeds ships two kinds of event data. Reach for raw logs when the decoded path doesn’t cover what you need:

​
The recipe bundle

​
Two access patterns

  • By contract: point Contract Logs at your protocol’s addresses and get a complete, ordered event log per contract. Decode in your application against the contract ABI.
  • By event signature: point Logs by Event Signature at a topic0 and capture that event chain-wide. Because popular signatures (Transfer, Approval) span the whole chain, scope reads to a block range. Enable the optional (topic0, contract) grouping when you frequently narrow to specific contracts within a signature.

​
Decoding the payload

Both recipes are intentionally raw: topic0 is the event signature hash, topic1…topic3 are the indexed parameters, and data is the ABI-encoded non-indexed payload as hex. Decode data (and interpret the indexed topics) against the event ABI in your application. Data Feeds delivers the complete, ordered, reorg-safe primitives; the decode layer stays under your control.

​
Notes and considerations

  • EVM only. Raw log extraction covers EVM event logs (topic0…3 + data). Solana program logs are a different model.
  • Heavier source. Logs come from the wide raw block data (all logs and transactions per block), so per-block volume is higher than the compact decoded recipes. tx_hash is recovered by joining each log to its sibling transaction row; drop that join if you don’t need it.
  • Scope popular signatures. A chain-wide Transfer/Approval feed is large. Bound it to a block range and run the ClickHouse path for live, reorg-safe ingestion.
  • Pair with decoded recipes. Use raw logs for the long tail and custom events; use the decoded recipes where a typed, ready-made shape already exists.

​
Get started

Data Feeds is in early access.

Try it today

Index any contract or event into your own infrastructure with the Moralis team.