Start here
Start with the right account, network and trading authority.
You can explore public markets without giving Omni custody of your wallet. Before trading, distinguish your signed-in Omni account, selected Hyperliquid master or subaccount, and connected signing wallet.
At a glance
Why It Matters
What traders and researchers should take away
- A public wallet profile is an inspection view, not authority to trade that wallet.
- Mainnet and testnet are separate environments; testnet balances do not fund mainnet.
How it works
What the product uses behind the scenes
- Omni session identity, linked-wallet ownership and selected trading scope are separate checks.
Notes
Things to know
- Google or email sign-in does not grant wallet funding authority.
- Deribit and IBKR remain DEV/private-beta features, not production Hyperliquid trading promises.
Guide
Steps
- Explore or sign in
Open the terminal to inspect markets. Use the sign-in flow when you need your saved account and linked wallets; follow the existing Connect Wallet guide for the wallet chooser.
- Confirm context
Check the Hyperliquid network and selected master/subaccount before acting. Verify the selected scope belongs to the intended master and the connected signer is the authorized wallet shown by the terminal. A subaccount or vault address can legitimately differ from its master signer; follow the actual Reconnect Scoped Wallet warning, not address inequality alone.
- Choose your next task
For trading, follow Fund and Withdraw, then First Order. For research, use the feature guides for liquidation risk, wallet intelligence, funding and news. Research output is not an instruction to trade.
Next
Open the workflow
- Explore the terminal Read public market data before granting trading authority.
Outcomes and Pro have different flows
Use the surface that matches the product; availability is network, territory and permission dependent.
- The Pro terminal provides the Market/Limit ticket described in the first-order guide. Outcomes uses a separate contract and review flow, not the same perpetual instrument.
- In Outcomes, wallet bridge funding first credits Core perps; a separate move funds Outcomes. To withdraw Core funds to a wallet, use Pro. Verify both legs rather than treating the bridge receipt as Outcomes credit.
- One-click Outcomes execution requires a funded account, approved builder and existing approved session. Review is the default; missing eligibility must not be bypassed.
Login is not Enable Trading
Each approval has a different purpose.
- A login signature proves wallet ownership. If you enabled two-factor authentication, also enter your authenticator code or an unused recovery code before expecting a full session. Enable Trading can require separate agent and builder-fee approvals; read the wallet prompt.
- Fund the selected account before enabling trading if the terminal shows Deposit Required Before Enable Trading.
- A stored agent may trade within its authority. Deposits, withdrawals and collateral transfers still require the appropriate wallet signature.
If the account looks wrong
Stop before signing or submitting an order.
- Recheck network, account scope and wallet address; a successful connection alone does not prove they match.
- Reconnect the intended wallet and wait for current balances, positions and orders. Do not submit against a stale account snapshot.
- If the session expired or was created on another DEV/PROD host, sign in again on the current host. Reconnecting a wallet or switching Hyperliquid networks does not renew the Omni session.
- If the account has no available collateral, use the funding guide; do not confuse equity with spendable collateral.
References
Implementation references
Wallet linking model
omni-terminal/docs/WALLET_LINKING_MODEL.mdSeparates user identity, wallet ownership and Hyperliquid scope.
Wallet scope safeguards
omni-terminal/docs/WALLET_SCOPE_SAFETY_PLAN.mdExplains signer and selected-scope checks.