Security
What HyperBase can do with your account, what it cannot, and how to check.
What we do not claim
While your authorization is active, our servers hold material that can place orders on your account without asking you again.
Authorization limits
That is what copying trades while you are away means, and it is not avoidable by adding a layer of cryptography.
So this is not zero-knowledge, and orders placed by a running strategy are not approved individually by your wallet. If that trade-off is not one you want, the honest options are to trade manually or not to authorize an agent at all — not to read a softer claim here and assume otherwise.
What limits the exposure instead: the key cannot move funds, the authorization expires on its own, and you can end it at any moment.
When it expires, and what that does to open positions
When it expires, or when you revoke it, trading stops completely and your positions are left exactly as they are. No closing orders are sent.
Expiry, renewal, and managing open positions
The execution engine drops the whole account from its sweep rather than trying to flatten it, because the exchange would reject every order from an unauthorized agent anyway.
The default authorization lasts 180 days from the signature, and you can renew it at any time with one more signature — no gas, no funds moved. We remind you before it lapses.
The consequence is worth being explicit about: an open position stays open and unmanaged — no stop, no copy of the trader exiting — until you authorize again. If you intend to stop, close what you want closed first, or revoke and then re-authorize to hand the position back to the copier.
What the agent wallet can do
Copy trading needs a key that can place orders while your browser is closed — a strategy cannot wait for you to approve each trade. Hyperliquid's answer is an API wallet (an “agent”): a separate key you authorize with your own wallet, by signature, that can trade for your account.
- It can place and cancel orders, and change trading leverage for your account.
- It cannot transfer or withdraw your funds, approve another agent, or move anything off the exchange.
That limit is enforced by Hyperliquid itself, not by HyperBase behaving well. It holds whether or not you trust us — which is the only kind of guarantee worth relying on.
Where the copy-trading key lives
The copy-trading agent key is generated on our server (never in your browser), then encrypted and stored before it is written to the database:
- AES-256-GCM, with a fresh random 96-bit IV per key, stored as
base64(iv ‖ tag ‖ ciphertext). The authentication tag is kept, so a tampered blob fails to decrypt rather than yielding a wrong key. - The key that encrypts it is a 32-byte secret held in the service's environment, not in the database — a database dump alone does not yield an agent key.
- The service that serves this page only ever encrypts — encryption happens when the key is created, and there is no decryption path in it at all. The only component that decrypts is the execution process, in memory, to sign an order. The plaintext key is never returned by any API and never reaches your browser.
What you can verify yourself
The agent address is shown on the strategies page, and the authorization itself is public on Hyperliquid: both the authorized agents for your account (extraAgents) and the builder fee ceiling you signed for (maxBuilderFee) can be read from any explorer or straight from the exchange's info endpoint. The ceiling is named on the authorization panel before your wallet ever asks you to sign it.
Revoking works the way the exchange defines it: an approval of the zero address, which is why revoking needs your signature too. Nothing about ending the authorization depends on our cooperation.