Trust Model
This section answers the questions an institution, auditor, or careful depositor asks before the questions an integrator asks: not what can the contracts do, but what can they not do, who holds which key, and how do I get out.
Everything here describes the contracts as deployed on Ethereum Mainnet and HyperEVM as of the date on each page. Where a page states a fact about a deployed contract, the function or on-chain record it comes from is named so it can be checked.
| Page | Question it answers |
|---|---|
| What the contracts cannot do | Which actions are impossible by construction, regardless of who holds a key. |
| Permission matrix | For each role: can it add risk, remove risk, take fees, change settings, or change code? |
| Key holders | Is each key a single wallet or a multisig? Is there a time delay? |
| Exit paths | For each product: how does a depositor get USDC back under normal, illiquid, operator-absent, and shutdown conditions? |
| Upgradeability | Which contracts can change after deployment, and by whom. |
| Fees | Who can set the performance fee, its ceiling, when a change takes effect, and where fees go. |
| Allowlist | What the access list gates, what it does not, and how a third party is admitted. |
| Safety controls | What pause, exit-all, shutdown and emergency redemption do to a depositor's position, and whether each can be undone. |
| Transparency | What a depositor can verify on-chain, what King's Vault watches daily, and what has been reviewed. |
| Risks | The risks a depositor takes on, by source, and where each is handled. |
King's Vault is a routing layer. It does not operate a lending market, an exchange, or a stablecoin. It holds depositor USDC in vault contracts and moves it into external protocols through strategy adapters; the yield, the liquidity, and a large share of the risk come from those protocols. The Introduction lists each underlying protocol and who governs it.
Why there are two prices
Every vault keeps two valuations of the same position, and every deposit or withdrawal is priced at whichever of the two is less favourable to the party transacting.
- The live value is what the strategies report right now: the vault's idle USDC plus each strategy's
totalAssets(). It moves continuously with interest, and for HLP it is a cached cross-chain state that can be hours old. - The confirmed value is the last settlement mark: a Keeper proposed it (
proposeValues) and an Admin confirmed it within one hour (confirmValues). It moves only when a round completes.
If the two agree, the price per share is the same either way. If they disagree — because yield has accrued since the last round, because a cross-chain report is stale, or because a quote-priced asset has moved — the vault does not guess which one is right. A depositor coming in receives shares at the higher of the two prices; a depositor going out is paid at the lower. The difference stays in the vault for the depositors who remain.
The reason is not caution for its own sake. Some of the assets a portal holds cannot be priced live on Ethereum: GHO is worth what its exit route (the Fluid pool, or the GSM) will convert it for, and an HLP position is worth what Hyperliquid reports on another chain. A single price would let whoever transacts first between two rounds take value from everyone else. Two prices, settled by two roles, make that impossible without preventing anyone from transacting. The mechanics are on the Architecture overview; the roles are in the Permission matrix.