flip/solana-models
1
0
Fork 0
mirror of https://github.com/FlipsideCrypto/solana-models.git synced 2026-02-06 09:41:44 +00:00
Code Issues Actions 14 Packages Projects Releases Wiki Activity
5399165667
solana-models/models/descriptions/tables/ez_events_decoded.md
tarikceric 5399165667
An 6390/llm context descriptions (#855) 
* description rules and fact_txs update

* blocks update

* idls and labels

* wip

* wip

* update desc

* update

* update doc rules

* update table desc per new rules

* updates
2025-07-16 12:26:39 -07:00

2.0 KiB
Raw Blame History

{% docs ez_events_decoded %}

Description

This table contains one row per decoded Solana record, mapping detailed program activity, event types, and instruction arguments as recorded on-chain. It only includes decoded data for programs for which we have the IDL (as listed in core.dim_idls). This table contains all the information in core.fact_decoded_instructions, but with additional extracted fields such as decoded_accounts, decoded_args, and decoding_error. For most analytics use cases, this table is preferred over core.fact_decoded_instructions due to its richer, more accessible structure. Each row represents a decoded event, supporting protocol usage analysis, event tracking, error monitoring, and attribution of accounts and signers.

Key Use Cases

  • Analyze decoded program activity and event types
  • Attribute events to accounts, signers, and protocols
  • Monitor protocol usage, event flows, and error rates
  • Support analytics on composable DeFi, NFT, and governance protocols
  • Enable flexible analytics on Solana program interactions and protocol activity

Important Relationships

  • Closely related to core.fact_decoded_instructions (for raw decoded instruction details), core.fact_events (for event context), and core.fact_events_inner (for inner/CPI events)
  • Use core.fact_decoded_instructions for raw instruction data if needed, but prefer this table for most analytics
  • Use core.fact_events and core.fact_events_inner for event-level context and protocol interactions
  • Joins with core.fact_blocks for block context and core.fact_transactions for transaction context

Commonly-used Fields

  • block_timestamp: For time-series and event sequencing analysis
  • block_id, tx_id, index, inner_index: For unique event identification and joins
  • program_id, event_type: For filtering by program or event type
  • decoded_instruction, decoded_accounts, decoded_args, decoding_error: For detailed event and error analytics
  • signers, succeeded: For user attribution and transaction outcome analysis

{% enddocs %}