About

King's Vault

King’s Vault is a permissioned DeFi gateway for address-based allowlisted users. The protocol simplifies access to curated on-chain strategies across Ethereum Mainnet and Hyperliquid (HyperEVM / HyperCore).

Documentation Purpose

This documentation describes the public V2 portals for:

Smart contract auditors — outlining architecture, trust assumptions, and areas requiring verification.
Protocol integrators — detailing function signatures, access control, and event interfaces.
Operations team — documenting workflows, deployed addresses, and operational procedures.

Documentation Scope and Verification

This documentation covers the V2 architecture used by Ethereum Network Lending, AAVE GHO Saving, and Hyperliquidity Provider (HLP). Their Performance Fee is 0%. Product behavior is described in the Introduction, with shared workflows and deployed addresses in the corresponding chapters.

AAVE GHO Staking uses a separate per-user V3 architecture. The pooled-share accounting, roles, and emergency procedures documented here do not apply to it.

Contract references describe the V2 interfaces. For integration or administration, use the target contract's deployed implementation, verified source, ABI, and current role grants. Published addresses alone do not establish source verification or operational readiness; see deployment verification status.

The Slither and Mythril pages describe analysis scope and methodology. They do not publish completed tool results, an independent audit opinion, or evidence that every current product has been audited.

Standards Implemented

Standard	Usage
ERC-4626	Basis for V2 tokenized vault shares and pricing. Lending and Saving use synchronous user flows.
Custom asynchronous redemption	HLP uses request, Keeper execution, and claim stages. Deposits are not described as an asynchronous queue. This is not a claim of full ERC-7540 interface compliance.
OpenZeppelin AccessControl	Role-based access in the documented V2 contracts; check each deployment's role grants.
OpenZeppelin Pausable	V2 vault pause mechanism; not a universal mechanism for all King's Vault products.
OpenZeppelin ReentrancyGuard	Guards on documented capital-movement paths; not a blanket safety guarantee.

State changes are executed on-chain, but operational progress still requires transaction submission by authorized actors. Cross-chain processing also depends on Circle's off-chain attestation service and message relaying; it is not an autonomous, wholly on-chain process.

External References

Contact

For audit inquiries or technical questions, please contact the King's Vault team.