BitGo lets self-custody clients connect directly to Hyperliquid perpetuals
The WalletConnect integration keeps BitGo approval policies in place while allowing eligible hot-wallet clients to trade on Hyperliquid without signing every order.
BitGo says eligible clients using its self-custody hot wallets can now connect to Hyperliquid and trade perpetual contracts through WalletConnect. The company's announcement frames the change as a way to combine venue-level trading speed with the custody and policy controls already configured in a BitGo wallet.
The setup does not mean funds remain entirely inside BitGo while orders execute. BitGo explains that assets move from the wallet's HyperEVM environment into the Hyperliquid application before a client can trade, then move back through the same path when the client withdraws. That distinction is the central custody caveat for anyone reading “self-custody” as a guarantee that no external trading venue is involved.
Connection starts on Hyperliquid, where the user selects WalletConnect and copies a pairing link. In BitGo, the user pastes that link into the wallet's Connect dApp flow and reviews the permissions before approving. BitGo's support documentation says the connection lets Hyperliquid view balances and activity and send approval requests, but it does not let the venue move funds without the wallet's authorization.
After the initial connection, a one-time signature enables gas-free trading. Clients can then place, modify and close perpetual orders without signing every action. Transfers into or out of Hyperliquid still require a separate signature, and a second authorized user may be required when a wallet's approval policy calls for multi-party sign-off.
The operational trade-offs
The product targets a familiar institutional problem: active desks want rapid order management, while treasury teams want controls that do not disappear when assets reach a trading venue. BitGo says the transfer process continues to use the same approval policy that governs other wallet movements, so the new connection changes the interface without removing those controls. Policy continuity is the selling point.
There are still several risks to separate. Hyperliquid perpetuals are leveraged derivatives, so losses can exceed the amount a user expects to risk when liquidation and funding mechanics move against a position. A WalletConnect pairing also creates an additional permission surface: users should verify the domain, inspect every signing request and disconnect stale sessions.
For BitGo, the announcement expands its role from custody and treasury movement into the workflow around a high-volume derivatives venue. For Hyperliquid, it lowers the setup burden for institutions that already use a qualified wallet provider. Neither statement proves that institutional volume will increase, and BitGo has not disclosed client counts or trading projections.
The practical takeaway is narrow. This is a connectivity and controls update, not a new investment product or a change to the risks of perpetual contracts. Institutions considering the route should test deposits, withdrawals, policy approvals and emergency disconnection procedures before committing meaningful capital. This article is informational and is not personalized financial advice.