vaults.fyi — Protocol Integration Questionnaire

1 Protocol Overview

Protocol name

Protocol version / product

Website & documentation URL

Upcoming network deployments?

2 Vault Architecture

Are your vaults ERC-4626 compliant?

Yes No Partially

Fully ERC-4626 — sections 2A–2C skipped. Scroll to 2D (Vault Discovery).

2A. Position Token

What token do depositors hold? e.g., aToken, cToken, receipt token, LP token

Example token address (mainnet)

If the receipt / LP token address differs by network or vault, list those too

Rebasing or share-based?

Rebasing (balance changes) Share-based (value per share increases) Other

Function to get the underlying asset address

If multi-asset, list supported deposit/redeem assets per vault/network

2B. Share Price / Exchange Rate

What is the exact call chain to compute price per share? Example: "Call vault.hook() → Teller address. Then teller.accountant() → Accountant address. Then accountant.getRate() → price per share."

2C. TVL

Function that returns total deposits in underlying terms

Function that returns currently available liquidity for instant withdrawals (if different)

2D. Vault Discovery

How should we find all vaults/markets? (check all that apply)

Factory contract — emits events on vault creation

Factory address(es) per network

Event signature

Deployment block per network

Registry / API

Contract address or API URL

Function or endpoint

Fixed list — provide addresses per network

Vault addresses (CSV or one per line)

Other

Vault creation model

Permissionless Governance-gated

3 Deposits & Withdrawals

3A. Deposits

Standard ERC-4626 deposit? (approve → deposit(assets, receiver))

Yes No

Deposit function signature

Target contract (vault itself, router, teller?)

Approval pattern

Standard ERC-20 approve Permit2 Other

Special parameters? (referral codes, minimums, deadlines)

Is deposit ever async / request-based?

Yes No

Request function signature

Claim / finalize function signature

Contract address(es)

Function(s) to read pending / claimable deposit state for a user

Typical wait time

Does the claim window expire?

Yes No

3B. Withdrawal Type

Instant — assets returned in same tx Request-redeem — submit request, claim later Cooldown — timer, then withdrawal window Other

3C. Withdrawal Queue Details

Queue / cooldown contract address

Request function signature

Claim / finalize function signature

Function(s) to read pending / claimable redeem state for a user

Typical wait time

Does the claim window expire?

Yes No

Standard ERC-4626 withdrawal? (redeem(shares, receiver, owner))

Yes No

Withdrawal function signature

Target contract

4 Reward Tokens

Do depositors earn reward tokens (beyond vault yield)?

Yes No

4A. Distribution Mechanism

On-chain rewards controller

Controller / distributor address

Claim function signature

Pending rewards function signature

Emission rate function signature

Off-chain / Merkle distribution

API for querying pending rewards per address

Auto-compounded — rewards fold into vault, no separate claim Other

4B. Reward Tokens

Token Symbol Address (mainnet) Networks

Same reward tokens on all networks?

Yes No

Emission rate type

Variable Fixed

5 Capacity & Limits

Are there deposit caps / supply limits?

Yes No

Function to read current cap on-chain (contract + signature)

Function to read utilization against cap

Does maxDeposit(address) return correct remaining capacity?

Yes No

6 Fees

Which fees apply? (check all)

Fee details

Type On-chain function Format

Fee taken from yield, principal, or at deposit/withdrawal time?

Fee recipient

7 Events & Indexing

Does the vault token emit standard ERC-20 Transfer events for mints/burns?

Yes No

Are there additional events beyond standard Transfer that we should index?

Yes No — standard Transfer only

Event signatures we should index

Auxiliary contracts that emit relevant events (staking, rewards, queue) Include addresses and event signatures.

Do raw indexed events map 1:1 to end-user LP balance changes?

Yes No

How should we normalize them?

Are user addresses always in standard from / to topic positions?

Yes No N/A

Which topic indexes or decoded event fields contain the user addresses?

If events come from an auxiliary contract, how do we map that emitter back to the vault?

8 Allocation & Risk

Does the vault deploy capital to underlying markets/strategies?

Yes No

Function to read the list of active allocations

Function to read amount allocated to each

Is there a curator/manager? Who?

Timelock on allocation changes?

9 Anything Else

Anything that doesn't fit above? e.g., multi-asset vaults, cross-chain mechanics, KYC / whitelist requirements, fixed-term or locked positions

Existing integrations we can reference?

Public GitHub repo