Deposit only after preview
Hyperliquid vault scanner
Hyperdaily treats vault deposits as a separate native Hyperliquid primitive. The wallet scan comes first; vaultTransfer signing only happens after a clear preview and revoke/withdraw path.
MetaMask or Rabby returns the selected public account. No private key, agent wallet, transaction, or message signature.
What this page solves
- Understand current vault exposure inside a wallet.
- Preview what a Hyperliquid vaultTransfer means before signing.
- Keep custody on Hyperliquid rather than sending funds to a pooled off-protocol wallet.
How Hyperdaily handles it
1. Connect walletMetaMask or Rabby returns the selected public account. Paste remains a fallback.
2. Read live contextFunding, whales, vaults, HyperEVM, risk, and local decision memory.
3. Preview before signingAny vault, builder, or agent action gets a separate preview and revoke path.
FAQ
Is Hyperdaily a custodian?
No. The vault path uses Hyperliquid vaultTransfer. Funds stay on Hyperliquid under protocol rules.
How do I exit a vault?
The revoke/exit path is a vault withdrawal transaction back to the user account.
Does the read-only scan deposit automatically?
No. Scan and deposit are separate steps.
Evidence standard
Hyperdaily separates public protocol facts from product interpretation, labels stale or missing evidence, and keeps connection separate from signing. Read the full data and scoring methodology.
Related Hyperdaily pages
Ready to connect a wallet?
Open your Hyperdaily briefing