King's Vault — Protocol Documentation
King's Vault is a permissioned gateway to on-chain yield: depositors hold one asset — ERC-20 USDC — and King's Vault's smart contracts route it into external protocols and back. The gateway is made of separate portals, each its own vault with its own strategies. King's Vault is a routing layer, not a market: it does not operate a lending pool, an exchange, or a stablecoin; the yield, the liquidity, and much of the risk of each product come from the protocol underneath it. Users deposit USDC on Ethereum Mainnet to access Aave and Morpho lending, Aave GHO savings, and Hyperliquid's HLP strategy.
Three things hold in every portal:
- Shares, not IOUs. Each vault is an ERC-4626 contract. A deposit mints share tokens to the depositor's own wallet; yield shows up as a rising price per share.
- 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 explicitly registered for that vault; a strategy can only return assets to the vault it belongs to.
- Everything is on-chain. Balances, strategy positions, the share price and every role change can be read from Ethereum at any time.
New here? Start with For Depositors. Evaluating the contracts? Start with the Trust Model.
Current Product Coverage
| Product | Yield source | Share token | Withdrawals |
|---|---|---|---|
| Ethereum Network Lending | Aave V3 / Morpho lending | kvUSDC |
Synchronous USDC withdrawal |
| AAVE GHO Saving | Aave sGHO savings | kvUSDC |
Synchronous USDC withdrawal |
| Hyperliquidity Provider (HLP) | Hyperliquid HLP | kvaUSDC |
Request, execution, and USDC claim |
Withdrawal availability depends on the product's liquidity and execution conditions. See exit paths, withdrawing and risks. Protocol fees are on the Fees page.
Quick Navigation
| Section | Description |
|---|---|
| For Depositors | Products, depositing, withdrawing, safety controls and risks, in plain language. |
| Introduction | Products, underlying protocols, architecture layers, and key terminology. |
| Trust Model | What the contracts cannot do, permission matrix, key holders, exit paths, safety controls, transparency, risks, upgradeability, fees, allowlist. |
| Architecture Overview | System architecture, roles, and dual pricing. |
| Workflows | V2 deposit, redemption, and operational flows with execution constraints. |
| Contract Reference | Per-contract function signatures, access control, and events. |
| Deployed Addresses | Mainnet contract addresses, chain selectors, and system contracts. |
| Security Analysis Methodology | Proposed tool scope and checks; not completed audit reports. |
Scope Summary
| Property | Value |
|---|---|
| Primary Asset | USDC (6 decimals) |
| Networks | Ethereum Mainnet; Hyperliquid's HyperEVM and HyperCore execution environments |
| Vault Model | ERC-4626-based V2 shares; custom asynchronous redemption for HLP |
| Cross-Chain Transport | Circle CCTP V2 (USDC burn-and-mint + state messages) |
| Yield Sources | Aave V3, Morpho Steakhouse USDC, Aave sGHO (Ethereum); HLP (Hyperliquid) |
| Access Model | Permissioned address allowlist |
| Settlement Model | Keeper proposal and Admin confirmation of V2 NAV epochs; not a guaranteed daily schedule |
Standards & Dependencies
| Standard / Library | Usage |
|---|---|
| ERC-4626 | Tokenized vault deposit / withdraw / preview interface |
| OpenZeppelin Contracts | AccessControl, Pausable, ERC20, SafeERC20, ReentrancyGuard |
| Circle CCTP V2 | Native USDC burn-and-mint bridge; state message relay between Ethereum and HyperEVM |
| Hyperliquid Docs | CoreWriter, L1Read precompiles, HLP vault |