Indexing Vaults

Two different needs, two different answers.

You just need your own vaults (or your users' vaults)

If all you care about is "give me the vaults for this wallet address, or for this list of wallet addresses" — use the Public API. No indexing, no event processing, no node operations required.

• POST /vaults/query/by-client-addresses takes a list of wallet addresses and returns the vaults owned by each.

• GET /vaults/{vault} returns full detail for a single vault.

See Reading Vault Data for a walkthrough and Reference → Public API for the full endpoint list.

You want to index every vault ever created

If you need a local view of all vaults created by Tesseract — for partner-wide dashboards, analytics, third-party data services, or anything you don't want routed through our API — index the on-chain VaultDeployed event.

• One event per vault, emitted by the Vault Deployer for each asset.

• The event exposes the new vault's address and its associated manager contracts (access manager, fee manager, withdraw manager, etc.).

• Event schema: Reference → Contract Methods → Vault Deployer.

There is one deployer per supported asset (USDC / WETH / WBTC), so the indexer needs to watch all three contract addresses.

Once you have the vault address, everything else is standard — ERC‑4626 views on the vault, the vault's WithdrawManager for scheduled withdrawals, and the Public API for performance / decoded history.