Set up. Inspect. Stay in control.
Start with the paper workspace, then connect an MT5 source for observation. This release does not submit live orders or hold trading funds.
Open the workspace
Open the engine to inspect BTC, ETH or gold public market data and run a paper route decision. Paper results are simulations; they are kept separate from MT5 source events and venue account balances.
To save an MT5 connection, connect an EVM externally owned wallet and sign the website’s login message. The signature establishes your session; it does not grant trading or withdrawal permission. Smart-contract wallet sign-in is not supported in this release.
Match exposure to capital
Capital matching estimates the collateral needed to reproduce an MT5 position. Enter the source lot size, broker contract size and destination budget. Reference contract sizes are 100 oz per lot for gold and 1 coin per lot for BTC or ETH; replace these with the specifications from your broker.
Notional exposure = lots × units per lot × price Initial margin ≈ destination notional ÷ selected leverage Actual exposure multiple = total notional ÷ account equity
The source account’s 500x or 1,000x setting is a margin ceiling. It is not the copy multiplier or the actual exposure. Preserving notional can require more destination collateral; a smaller allocation requires a smaller copy. Changing the venue leverage alone does not change the profit or loss on the same notional position.
Hyperliquid market rules are read on demand for BTC, ETH and xyz:GOLD. Quotes and tiers can change; fees, adverse price moves and existing positions need additional margin. The calculator is an estimate, not a balance transfer, venue authorization or execution instruction.
Open Capital matching → · Compare the FX / gold venue candidate
Install the MT5 bridge
Download Bridge 1.0.0 · EX5 + source + setup guide ↓
- In the engine’s Connections view, enter your MT5 account number and the exact broker server name. Create a connection and copy its device token.
- In MT5, choose File → Open Data Folder. Copy HyperMatchBridge.ex5 into MQL5/Experts and refresh Expert Advisors in the Navigator.
- Open Tools → Options → Expert Advisors. Enable WebRequest for https://hypermatch.org. Attach the EA to one chart of the source account.
- Paste the token into InpDeviceToken. Keep InpBridgeUrl on the same deployment that issued it. Wait for PAIRED / PAUSED, then select START RELAY.
- Keep MT5 running and connected. Observe the next source deal in the website’s event log. The EA does not submit or modify MT5 trades.
To simulate routing from this source, select Enable paper routing on its connection. Only eligible new events after opt-in are considered; observation alone does not start the simulation. Stop paper routing to turn off that permission.
One bridge observes all symbols on the account. No wallet private key, broker password or DLL permission is needed. Attaching or restarting it does not backfill old trades.
Read the event states
- Accepted / observed. The server has stored a source event. It is not proof of a venue fill.
- blocked_mapping. A position reversal requires a verified reduction/opening plan before it can be routed.
- observed_stale. The received source event is old. It is retained for inspection, not traded.
- Paper routing state. A queued, processing, completed or blocked simulation has its own state and receipt. It does not change the meaning of source acceptance and is not a real fill.
- Local REVIEW. The bridge has paused after a stale event, invalid payload or storage problem. Inspect source and destination positions before restarting.
Delivery retries reuse the same event identity. Revoking a device token stops future authorized ingestion. Pausing the EA stops capture and delivery; trades during that pause are not replayed on resume.
Funds & withdrawals
The Deposit & withdraw workspace separates exchange transfers from wallet transfers. Personal deposit addresses and real withdrawals will only appear after the custody and settlement service is provisioned and verified. Paper balances cannot be redeemed. Existing self-managed venue accounts remain accessible through the official venue.
For Hyperliquid, the documented Arbitrum route starts with native USDC and a little ETH for transaction gas on Arbitrum One (chain ID 42161), held in your own wallet. Connect that wallet at the official venue and use its Deposit flow. Check the displayed network, token, fees and destination before signing. Sending USDC to your wallet alone does not fund the HyperCore trading balance.
Paper routing and the capital calculator require no deposit. Funded testnet execution has not completed verification and live trading remains disabled. When a venue is enabled, calculate capital from the intended position and keep a margin buffer; a high source-account leverage setting does not reduce the destination’s own requirements.
Account equity and withdrawable funds are different amounts. Open positions, required margin, pending transfers, fees and settlement rules can limit what is available. A withdrawal request being accepted is not the same as arrival in the destination wallet.
The current account readout covers the native HyperCore perpetual account only. It excludes spot and separate HIP-3 DEX balances; use the venue for the full account view.
Open the official Hyperliquid app · Official deposit guide · Independent exit steps
Bridge API
A wallet-authenticated session creates a device through POST /api/devices. The returned token is bound to its MT5 account and server. Heartbeat and source event requests use that token over HTTPS.
POST /api/bridge/heartbeat
Authorization: Bearer <device-token>
Content-Type: application/json
{
"accountLogin": "123456",
"server": "Broker-Demo",
"bridgeVersion": "1.0.0",
"terminalBuild": 5400,
"queuedEvents": 0,
"connected": true
}POST /api/bridge/events accepts the following source payload. Account and ticket IDs stay strings; volume is in MT5 source lots.
{
"eventId": "mt5:Broker-Demo:123456:987654",
"accountLogin": "123456",
"server": "Broker-Demo",
"symbol": "XAUUSD",
"side": "buy",
"entry": "in",
"volume": "0.01",
"price": "2500.00",
"occurredAt": "2026-09-19T08:00:00.123Z",
"dealId": "987654",
"positionId": "123789"
}A 2xx response acknowledges durable ingestion, including identical duplicates. A 409 conflict requires review; 401/403 requires checking the device binding. The endpoint observes events and never places a live order.