Hyperoru supports trading on Hyperliquid and Binance Futures. This guide covers wallet configuration, testnet environments, and trading mode management.
Hyperliquid Hyperliquid is an L1 blockchain optimized for on-chain perpetual trading. Hyperoru supports two wallet types for authentication.
Wallet types Direct wallet authentication using the account’s private key. This grants full trading permissions. curl -X POST https://api.hyperoru.com/api/hyperliquid/wallets \ -H "Content-Type: application/json" \ -d '{ "trader_id": "trader-uuid", "wallet_type": "private_key", "private_key": "0xYourPrivateKey" }'
Private keys are AES-encrypted at rest using HYPERLIQUID_ENCRYPTION_KEY. Never share your private key or encryption key.
Hyperliquid agent wallets are delegated keys with restricted permissions. They can trade on behalf of the main wallet without having withdrawal access. curl -X POST https://api.hyperoru.com/api/hyperliquid/wallets \ -H "Content-Type: application/json" \ -d '{ "trader_id": "trader-uuid", "wallet_type": "agent", "agent_private_key": "0xAgentKey", "agent_address": "0xAgentAddress", "vault_address": "0xMainWallet" }'
Agent keys are the recommended approach for automated trading. They limit exposure if the key is compromised — the agent can trade but cannot withdraw funds.
Testnet vs mainnet Toggle between Hyperliquid testnet and mainnet per trader:
curl -X PUT https://api.hyperoru.com/api/hyperliquid/wallets/{wallet_id}/network \ -H "Content-Type: application/json" \ -d '{"testnet": true}'
Network API Base URL Purpose Mainnet https://api.hyperliquid.xyzLive trading with real funds Testnet https://api.hyperliquid-testnet.xyzPaper trading and strategy validation
Binance Futures Binance Futures uses API key + secret authentication with HMAC-SHA256 request signing.
Setup curl -X POST https://api.hyperoru.com/api/binance/credentials \ -H "Content-Type: application/json" \ -d '{ "trader_id": "trader-uuid", "api_key": "your-binance-api-key", "api_secret": "your-binance-api-secret" }'
Testnet vs mainnet curl -X PUT https://api.hyperoru.com/api/binance/credentials/{credential_id}/network \ -H "Content-Type: application/json" \ -d '{"testnet": true}'
Network API Base URL Purpose Mainnet https://fapi.binance.comLive trading with real funds Testnet https://testnet.binancefuture.comPaper trading and strategy validation
Trading mode Each trader has an active trading mode that determines which exchange receives orders:
curl -X PUT https://api.hyperoru.com/api/traders/{trader_id}/trading-mode \ -H "Content-Type: application/json" \ -d '{"mode": "hyperliquid"}'
Mode Description hyperliquidOrders route to Hyperliquid binanceOrders route to Binance Futures
Switching trading mode does not close open positions on the previous exchange. Close positions manually before switching.
Watchlist management Each trader maintains a watchlist of symbols to monitor. The watchlist determines which symbols appear in market data context, signal evaluation, and strategy execution.
curl -X PUT https://api.hyperoru.com/api/traders/{trader_id}/watchlist \ -H "Content-Type: application/json" \ -d '{ "symbols": ["BTC", "ETH", "SOL", "ARB", "DOGE"] }'
Querying available symbols curl https://api.hyperoru.com/api/crypto/symbols
Returns the full list of tradeable symbols on the active exchange.
Security best practices
Use agent keys On Hyperliquid, prefer agent keys over direct private keys. Agent keys cannot withdraw funds.
Restrict API permissions On Binance, create API keys with only Futures trading permission. Disable spot, withdrawal, and margin.
IP whitelisting On Binance, restrict API key access to your server’s IP address.
Start on testnet Validate strategies on testnet before committing real funds. Both exchanges offer full-featured testnet environments.
