Skip to main content

Architecture & Security

How VibeTrade connects to Hyperliquid — the non-custodial signing model, the networks it supports, the builder fee, and how live data reaches the app.

VibeTrade is a non-custodial front-end. Your wallet signs all on-chain actions, and orders are submitted directly to the Hyperliquid protocol — there is no relay or custody layer between you and the network.

Networks​

VibeTrade supports both Hyperliquid networks — Mainnet and Testnet — and you switch between them in CONSOLE → GENERAL → NETWORK. The choice is remembered for this device; switching reloads the page and asks you to re-authorize the trading session for the new network.

All Hyperliquid signing happens on Arbitrum — Arbitrum One on mainnet, Arbitrum Sepolia on testnet — regardless of which chain your wallet is currently set to. If your wallet is on a different chain at signing time, VibeTrade asks it to switch first.

Wallet connection​

VibeTrade uses wagmi and supports three connector families:

  • Injected — browser-extension wallets such as MetaMask, Rabby, Brave, OKX, and TronLink.
  • WalletConnect — most mobile wallets via QR or deep link, when WalletConnect is configured for the deployment.
  • Coinbase Wallet — the Coinbase extension and mobile app.

Every Hyperliquid action is signed as an EIP-712 typed message against the active signing chain.

Trading session​

VibeTrade splits signing duties between two keys:

  • Master wallet — your connected wallet. Used to authorize the trading session and other one-off, security-sensitive actions.
  • Agent wallet — a per-device session key VibeTrade creates in your browser and uses to sign trade and account-management actions.

The agent wallet cannot withdraw funds or move balances out of your wallet. Withdrawals, transfers, and sends still require a master-wallet signature.

Authorization​

The first time you trade on a new network, VibeTrade walks you through the Trading Authorization dialog in TRADE:

  1. (only if your wallet has no referrer yet) Sign Referral Registration to link the wallet to VibeTrade's referral.
  2. Sign Trading Authorization — this commits the builder-fee cap (see Builder fee below).
  3. Setup Complete — you can now place orders.

Separately, the per-device agent wallet is authorized by its own one-time master-wallet signature when you enable trading. That agent key is scoped to the current network and persists across page reloads on the same device, so you don't re-sign every session.

If your wallet is on the wrong chain at signing time, VibeTrade requests a chain switch first; failures show a Retry button.

Revocation​

Use Reset in CONSOLE → GENERAL → NETWORK's Wallet card to clear the agent wallet for the current device. The next order asks you to authorize again. Your master wallet and any other devices are unaffected.

Builder fee​

VibeTrade is registered as a Hyperliquid builder, and trades placed through VibeTrade carry a small builder fee that funds the project. The maximum fee is capped by the amount your Trading Authorization signature commits to, and you'll be asked to re-authorize when that approval expires or when you switch network.

When your wallet has no referrer yet, VibeTrade offers to register its referral during setup. Registering is permanent — Hyperliquid does not allow re-linking once a referrer is set — and it applies a discounted Hyperliquid fee tier, bringing your overall trading cost down.

Live data and refresh​

Live data — prices, the order book, the trade tape, and your account state — streams over WebSocket, while one-shot snapshots are read over REST.

  • Your master address streams in real time over WebSocket.
  • Watched addresses are refreshed over REST roughly every 30 seconds to keep request volume reasonable, which is why their cards occasionally show a Sync delayed badge.

The Hyperliquid API enforces request rate limits. When VibeTrade is being paced upstream, the refresh icon in the page header spins to signal that fresh data will land momentarily.