Skip to main content

Kong

Kong is a real-time/historical EVM indexer and analytics platform designed to make it easy to index EVM logs, enrich blockchain data, and query indexed data via GraphQL. It comes pre-configured with an index over Yearn's v2 and v3 vault ecosystems. For more detailed docs, reference deepwiki.

Key Features​

Event Sourcing Architecture​

  • Stores EVM logs and contract snapshots in PostgreSQL without transformation
  • Supports index replay without re-extracting data from blockchain
  • Handles events out of order for faster historical indexing

Hook System​

Three types of custom enrichment hooks:

  • Snapshot Hooks: Process recurring snapshots of contracts
  • Event Hooks: Process and enrich blockchain events
  • Timeseries Hooks: Generate time-series analytics data

Real-Time Webhooks​

  • Real-time notifications triggered during indexing
  • HMAC-SHA256 authentication
  • Configurable filtering by chains and contract addresses

Domain Modeling with "Things"​

  • Dynamically created entities (analogous to "entities" in conventional ETL)
  • Used as sources for further indexing
  • Supports hierarchical indexing (e.g., Registry → Vaults → Strategies)

GraphQL API​

Base URL​

Example Queries​

List Yearn Vaults on mainnet​

query MainnetVaults {
  vaults(chainId: 1) {
    address
    name
    symbol
  }
}

List Yearn v2 vaults on all chains​

query GetV2VaultAddresses {
  vaults(vaultType: 2) {
    chainId
    address
    name
    symbol
  }
}

Query last 100 deposit events for specific vault​

query GetDeposits {
  deposits(chainId: 1, address: "0xBe53A109B494E5c9f97b9Cd39Fe969BE68BF6204") {
    amount
    shares
    recipient
  }
}

Query Timeseries Data for specific vault​

query Timeseries {
  timeseries(
    label: "tvl-c",
    component: "tvl",
    chainId: 1,
    address: "0xdA816459F1AB5631232FE5e97a05BBBb94970c95",
    limit: 1000
  ) {
    chainId
    address
    label
    component
    value
    time
    period
  }
}

Database Schema​

Core Tables​

thing​

Domain object definitions (vaults, strategies, etc.)

  • chain_id, address, label, defaults (JSONB)

snapshot​

Latest contract snapshots with hook data

  • Stores contract state and enriched hook data
  • JSONB fields for flexible schema

evmlog​

Raw EVM logs with hook enrichments

  • Full event history with args and hook data in JSONB
  • Limited history on transfers, deposits, withdraws, approves

evmlog_strides​

Track which blocks have been indexed

  • Prevents duplicate indexing
  • Identifies gaps in coverage

output​

Timeseries data from timeseries hooks

  • TVL, APY, PPS calculations
  • Time-series analytics
Last updated on