Deployed Addresses & Identifiers
This page covers the active V2 portals: Ethereum Network Lending, AAVE GHO Saving, and Hyperliquidity Provider (HLP). AAVE GHO Staking uses a separate V3 architecture and is hidden from the public mainnet frontend; the V2 addresses and operational roles below must not be used as its deployment manifest.
Product Address Map
Underlying protocol references are not interchangeable with King's Vault strategy adapters or deposit recipients. Users deposit through their product's King's Vault vault, not by sending tokens directly to an underlying address. See the AAVE GHO Saving introduction for its product flow.
King's Vault Core Contracts
The routers are HyperEVM smart contracts that interact with HyperCore; they are not contracts deployed on HyperCore. Read-only checks on 2026-09-02 confirmed non-empty code at all five router addresses on HyperEVM. Code presence alone does not verify source code, permissions, or operational readiness.
HyperCore System Contracts (HyperEVM)
| Contract |
Address |
Description |
| CoreWriter |
0x3333333333333333333333333333333333333333 |
Send actions from HyperEVM to HyperCore |
| L1Read Precompile |
0x0000000000000000000000000000000000000800 |
Read HyperCore state (start address) |
HyperCore Vault
| Entity |
Address |
| HLP Vault |
0xdfc24b077bc1425ad1dea75bcb6f8158e10df303 |
CCTP Infrastructure
Ethereum Mainnet
| Contract |
Address |
Description |
| CCTP TokenMessenger |
0x28b5a0e9C621a5BadaA536219b3a228C8168cf5d |
Initiates cross-chain USDC burns |
| CCTP MessageTransmitter |
0x81D40F21F12A8F0E3252Bccb954D722d4c464B64 |
Receives messages and verifies Circle attestations on-chain; Circle's off-chain service produces the attestations |
HyperEVM Mainnet
| Contract |
Address |
Description |
| CCTP TokenMessenger |
0x28b5a0e9C621a5BadaA536219b3a228C8168cf5d |
Initiates cross-chain USDC burns |
| CCTP MessageTransmitter |
0x81D40F21F12A8F0E3252Bccb954D722d4c464B64 |
Receives messages and verifies Circle attestations on-chain; Circle's off-chain service produces the attestations |
| CoreDepositWallet |
0x6B9E773128f453f5c2C60935Ee2DE2CBc5390A24 |
Receives USDC from the Router for HyperCore spot deposit, after CCTP minting to the Allocator and allocation to the Router |
CCTP Domain Identifiers
| Chain |
Domain ID |
| Ethereum |
0 |
| HyperEVM |
19 |
Reference: Circle Supported Chains & Domains
| Asset Type |
System Address Format |
Example |
| General tokens |
First byte 0x20, with the token index encoded big-endian in the remaining 19 bytes |
USDC index 0 → 0x2000000000000000000000000000000000000000 |
| HYPE (native) |
Fixed address |
0x2222222222222222222222222222222222222222 |
Hyperliquid's spotMeta response was checked on 2026-09-02: USDC is token index 0; index 5 is JEFF, not USDC. A system transfer address is distinct from an ERC-20 token contract and from CoreDepositWallet. This table describes identifiers, not a substitute for the approved deposit/withdrawal flow; verify the asset, network, linked token metadata, and transfer direction before integration. See the official system-address and transfer rules and spot metadata API.
CoreWriter Action IDs
| ID |
Action |
ABI Encode Type |
Header |
| 1 |
Limit Order |
(uint32, bool, uint64, uint64, bool, uint8, uint128) |
0x01000001 |
| 2 |
Vault Transfer |
(address, bool, uint64) |
0x01000002 |
| 3 |
Delegate |
(address, uint64, bool) |
0x01000003 |
| 6 |
Spot Send |
(address, uint64, uint64) |
0x01000006 |
| 7 |
USD Transfer |
(uint64, bool) |
0x01000007 |
| 10 |
Cancel Order (by OID) |
(uint32, uint64) |
0x0100000a |
| 11 |
Cancel Order (by CLOID) |
(uint32, uint128) |
0x0100000b |
| 13 |
Send Asset |
(address, address, uint32, uint32, uint64, uint64) |
0x0100000d |
API Endpoints (Hyperliquid L1)
Base URL: https://api.hyperliquid.xyz/info
| Query |
Payload |
Returns |
| Vault Details |
{"type": "vaultDetails", "vaultAddr": "0xdfc24b..."} |
Portfolio, APR, followers, withdrawal lockup |
| User Vault Equities |
{"type": "userVaultEquities", "user": "0x..."} |
Equity per vault |
| Clearinghouse State |
{"type": "clearinghouseState", "user": "0x..."} |
Perpetual positions and margin state |
| Spot Clearinghouse State |
{"type": "spotClearinghouseState", "user": "0x..."} |
Spot token balances and holds |
The spot and perpetual endpoints are separate; see the official spot balance API.
Risk Parameters
| Parameter |
Value |
Description |
| Virtual Offset |
10^12 |
Share precision inflation applied in dual-pricing math (18 − asset.decimals() for USDC) |
| Shares Decimals |
18 |
Standard ERC-20 decimals; _decimalsOffset() = 12 used internally in share conversion |
| Performance Fee |
0% (feeRate = 0) |
Current configuration for Ethereum Network Lending, AAVE GHO Saving, and Hyperliquidity Provider (HLP); the V2 fee mechanism remains configurable. |
| Default PPS |
1.000000 |
Initial price per share |
The Controller's feeRate(vault) returned 0 for all three V2 vaults using Ethereum block 25887436, checked at 2026-09-02 05:12:27 UTC. The denominator is 1_000_000; this is a dated configuration observation, not a guarantee that a configurable rate cannot change. It does not apply to GHO Staking V3.
Deployment Verification Status
The address map identifies the current product endpoints; it is not a complete source-verification or audit manifest. Deployment verification requires the source commit, build settings, constructor/initializer inputs, proxy implementations where applicable, deployment transactions, and effective privileged roles. Addresses and permissions must be checked for the specific product and chain, not inferred from another product or an older source snapshot. GHO Staking uses a separate V3 deployment.