Subgraph

GraphQL indexes for vault, manager, and transaction data

Chamber's subgraphs are The Graph Protocol deployments that index vault state, deposits, withdrawals, trades, and manager activity. They are the primary source for analytics, dashboards, leaderboards, and any UI that needs to list or filter vaults.

Repo: dhedge-v2-subgraphs

When to use the subgraph

• List or search vaults — by manager, denomination asset, chain, performance.

• Reconstruct vault history — deposits, withdrawals, trades, fee events over time.

• Power a leaderboard or directory — see leaderboard & ranking.

• Build portfolio views — a depositor's positions across multiple vaults.

For live state (current NAV, open positions), call the contracts directly or use the SDK — subgraphs lag the chain by a few blocks.

Chain coverage

Separate subgraph deployments exist per chain:

• Polygon

• Optimism

• Arbitrum

• Base

• Plasma

• Ethereum

• HyperEVM

Each chain has its own GraphQL endpoint. There is no single cross-chain endpoint — aggregate on the client side.

Endpoints: Per-chain GraphQL URLs are maintained in the subgraph repo README.

What gets indexed

Full schema is in the subgraph repo's schema.graphql. The schema evolves with contract upgrades — pin your integration to a specific subgraph version if you depend on exact field shapes.

See also

• SDK — for live onchain reads

• Leaderboard & ranking — how the app uses this data

• Contract addresses — the contracts the subgraph indexes