For Depositors
This section describes King's Vault from the depositor's side: what the portals are, how to deposit, how withdrawals work, and what to expect while your USDC is deployed. It uses plain language and links to the Trust Model and the Protocol chapters for the contract-level detail behind each statement.
Three things to know first
Shares, not IOUs. Every portal is an ERC-4626 vault. When you deposit USDC the vault mints share tokens to your own wallet; yield shows up as a rising price per share. Your position is the balance in your wallet, not an entry in anyone's ledger. See Depositing.
Funds only go where the contract allows. USDC moves directly between a vault and its strategies. The Controller only instructs those moves and keeps the books — it never holds funds — and it can only target strategies that were explicitly registered for that vault; a strategy can only deliver assets back to the vault it belongs to. Adding or removing a strategy is a separate, restricted, on-chain action. See What the contracts cannot do.
Everything is on-chain. Vault balances, strategy positions, the share price, every allocation and every role change can be read from Ethereum at any time. There are no statements to trust. See Transparency.
Pages
| Page | What it covers |
|---|---|
| Products | The live portals, where each one's yield comes from, its share token and its withdrawal model. |
| Depositing | Allowlist, wallet, approve and deposit, what happens after the deposit lands. |
| Withdrawing | Synchronous and asynchronous withdrawals, displayed versus received amounts, what makes a withdrawal revert. |
| Safety controls | What pause, exit-all, shutdown and emergency redemption do to your position. |
| Risks | The risks a depositor takes on, by source. |
What King's Vault does not do
King's Vault does not exchange fiat, does not hold client funds outside the vault contracts, and does not verify identity; the allowlist contains wallet addresses only. Fiat on- and off-ramps are handled by regulated partners.