vaultsDocumentation
Open app

Vaults documentation

Vaults are autonomous onchain funds that mirror the positions of a chosen public account inside fixed, published limits. The account being followed is a read-only signal: it never holds custody, never signs, and cannot be given control later. Everything here describes what the contracts in this repository actually do — each page is labelled with whether it is implemented, testnet-only, blocked, or design.

Start hereUse VaultsFind a source worth following, understand what a vault actually holds, deposit, and know exactly how to get out.Introduction · Getting started · Depositing · Withdrawals and in-kind exitsFor developersBuild with VaultsContract topology, the TypeScript SDK, the read-only HTTP API, and the events every sync emits.Contracts · SDK · API · Events and receipts

Quickstart

  1. Find a source accountBrowse the market. Every listing shows whose positions it mirrors and four separate verification facts — what each one proves.
  2. Read what the vault holdsOpen the vault sheet: current NAV, every position, allocation, and exactly where the vault currently differs from its source.
  3. DepositYou receive vault shares. The source account cannot trade, withdraw, or sign for the vault — it holds no permissions at all.
  4. Exit whenever you wantBurn shares for your pro-rata slice of everything the vault holds. That path has no pause switch and consults no price feed.

Core concepts

Source accountsA read-only signal with no permissions, and the split that keeps identity out of the trust path.Mirror vaultsThe contract that holds the assets: what it can do, and the things it deliberately cannot.Mirror mathHow a source’s position change becomes a vault-sized trade, and every cap applied on the way.Synchronisation lifecycleIn sync, pending, awaiting keeper, paused, unpriceable — what each state means and how it clears.

Protocol status

Network
robinhood-testnet
Chain ID
46630
Block time
~141 ms
Indexed block
269
Mainnet
Not deployed. The deploy script refuses chain 4663 outright.
Audit
None. The protocol is unaudited.

Open launch gate

It is not yet established that Fomo accounts hold Robinhood Chain positions. No such claim is made anywhere in this system until proven with a live FomoScan key, a real handle, and observable onchain activity. All eight gates.

  • How Vaults worksImplementedThe full path from a source account changing a position to a vault holding the same asset.
  • Mirror mathImplementedHow a source’s position change becomes a vault-sized trade, and every cap applied on the way.
  • Risk constraintsImplementedThe six articles of the risk constitution, fixed for the life of a vault.
  • Withdrawals and in-kind exitsTestnet onlyTwo exits with different guarantees. One of them keeps working when everything else has failed.
  • Security modelImplementedWhat is trusted, what is not, and the blast radius of each trusted thing failing.
  • Known limitationsImplementedThe residual risks that are real, stated plainly rather than concluded away.

Security and limitations

V1 is not trustless. It depends on keeper liveness, curated asset metadata, price adapters, an off-chain indexer for history, and a base asset upgradeable by the chain’s bridge governance. Those are named individually rather than summarised away in Known limitations, alongside the threat model and the security model.

Everything