Skip to content

Transparency

King's Vault holds depositor funds only in verified smart contracts on public chains. This page lists what a depositor can verify without trusting anyone, what King's Vault itself watches, and what has been reviewed.

Status as of 2026-09-30.

What you can verify yourself

Fact Where to read it
Your share balance and the vault's total assets The vault contract: balanceOf, totalAssets, totalSupply
The current price per share convertToAssets(1e6) on the vault, or the portal
Which strategies are registered for a vault and how much each holds Controller.strategies(vault) and Controller.totalStrategyAssets(vault); each strategy's totalAssets
Every allocation, recall, valuation and withdrawal Transactions and events on the Controller and the vault (FundPushed, ValuesProposed, ValuesConfirmed, RedeemRequested, RedeemExecuted, Claimed); upgrades, role changes and strategy changes are logged as events
Who holds which role RoleGranted / RoleRevoked events on the Controller and the vaults; summarised on Key holders
That the deployed code matches the published source Etherscan source verification for the addresses on Deployed Addresses; see its verification status for what the address map does and does not establish
Whether a contract has been upgraded Upgraded events on the Controller and the HyperEVM Allocator proxies; see Upgradeability

Strategy positions live in the underlying protocols and can be read there too: the aEthUSDC and Steakhouse vault balances of AaveV3Strategy and SteakhouseStrategy, the sGHO balances of the GhoSavingFluidStrategy deployments and of GhoSavingStrategy, and the HLP position of the Allocator on Hyperliquid.

What King's Vault watches

Every day King's Vault runs an external watch over each dependency a portal relies on, and records the result:

  • Aave V3 — USDC market status, utilisation, pauses and governance actions.
  • Morpho Steakhouse USDC — vault status, caps and curator actions.
  • Aave GHO — sGHO parameters, GHO peg; GSM inventory and fees for the legacy route.
  • Fluid — GHO/USDC pool depth, fee and withdrawal limits (the current USDC ↔ GHO route).
  • Hyperliquid — HLP vault status and returns, HyperEVM and HyperCore availability.
  • Circle CCTP — bridge availability on both domains.
  • Stablecoin pegs — USDC and GHO.
  • King's Vault's own roles and contracts — role changes, upgrades, pauses and shutdowns on every vault and the Controller.

The portals' APY figures are read from the underlying protocols and updated daily; valuation rounds (ValuesProposed → ValuesConfirmed) are visible on-chain as they happen.

What has been reviewed

The King's Vault V2 contracts were reviewed by Adevar Labs in May 2026. The Slither and Mythril pages describe the static-analysis scope and methodology applied to the codebase. Neither replaces a depositor's own reading of the Trust Model: the structural guarantees on these pages hold because of how the contracts are written, not because of who has looked at them.

What is not published

King's Vault does not publish the identities of key holders beyond what is on-chain, does not publish operational allocation targets, and does not publish APY forecasts. Historical APY shown on a portal is what the underlying protocol paid, not a King's Vault projection.