Separate permissions. Clear exits.
Signing in, observing an MT5 source and authorizing venue trades are different actions. Each should have a defined scope and an independent way to stop it.
Three permission boundaries
Wallet login
A time-limited, single-use message verifies your wallet address and creates a website session. It does not approve token spending, venue trades or withdrawals. Current sign-in supports EVM externally owned accounts.
MT5 device token
The token permits heartbeat and source-event ingestion for its exact account/server binding. It expires after 30 days and can be revoked in Connections. It is stored as a hash on the server. Keep the original token private, including saved MT5 presets.
Venue trading authority
A future live adapter requires a separate, venue-specific approval. Its signer must only allow validated trading actions within account limits. This release has no enabled live signer and does not ask you to deposit funds into HyperMatch.
What the bridge can observe
The EA reads source account identity and new buy/sell deal details: ticket, position, symbol, side, volume, price and time. It does not require your broker password or wallet private key, and it has no MT5 order-submission code.
Pairing proves that a token-bearing bridge reports the matching terminal account. It is not an independent broker attestation of account ownership. Source events are stored for your signed-in wallet; local event journals also remain on the terminal computer.
Your independent exit
- Pause new source relay in MT5. Review any pending events before restarting.
- Inspect open orders and positions directly at the official venue. Pausing HyperMatch does not close positions.
- Revoke any venue trading agent at the venue. Revoking an MT5 device token only stops source ingestion; it is a separate control.
- Use your owner wallet to reduce exposure and request the funds available for withdrawal under the venue’s rules.
The official venue remains your account access point if HyperMatch is unavailable. Keep its address, network and account details separately. Never send funds to an address presented as a HyperMatch support or recovery wallet.
Before live execution
Compilation, market-data access and a deployed website do not demonstrate a complete trading system. Live execution requires funded testnet order/fill reconciliation, permission and revocation tests, recovery from uncertain outcomes, and verified instrument mappings.
Venue risks remain: oracle or market failure, liquidation, contract vulnerabilities, counterparty risk and restricted withdrawals. Permission limits and non-custodial account design do not remove those risks.
View current capabilities →