Everstrat Docs home
DevelopersData

Subgraph and data access

When to use the GoldSky endpoint versus direct RPC reads in frontend or tooling integrations.

07 / Data architecture

History from the subgraph. State from RPC.

Open
History from the subgraph. State from RPC.AMM, ExitQueue, and EVE events feed GoldSky history, while direct Ethereum RPC reads supply current state to the app and integrations.READEVENTSGRAPHQLLIVE READSETHEREUMOn-chain contractsAMM · ExitQueue · EVELIVE STATEEthereum RPCDirect contract readsHISTORYGoldSky subgraphIndexed events + entitiesCONSUMERSApp & integrationsChoose the source by needINDEXED HISTORYActivity · requests · batchesCURRENT STATEBalances · prices · allowances
API / RPC readEvent indexing

Use GoldSky for activity, user aggregates, and batch or request history. Use direct RPC for balances, allowances, paused state, live prices, and current-batch request gating. Indexed history can lag the chain.

Use The Subgraph For

  • activity history
  • aggregate profile state
  • queued burn lifecycle history
  • batch metadata across time

Use Direct RPC Reads For

  • current balances
  • allowance
  • paused state
  • live price views
  • claimable ETH and request eligibility across all discovered pending batches
  • current timelock execution eligibility and Registry state

Last updated on

Transaction modal and status UX

Shared receipt-based outcomes, duplicate protection, and resumable confirmation.

Events, entities, and integrations

The minimum event and entity set required to integrate with frontend or analytics consumers.

On this page

Use The Subgraph ForUse Direct RPC Reads For