出典確認済みリサーチ: GMX

Decision Matrix

Source Map

• GMX Docs: Getting Started (gmx-sdk-getting-started)
• GMX Docs: Delegated trading integration (gmx-delegated-trading)
• GMX Docs: Frontend Integration (gmx-frontend-integration)
• GMX Docs: Order Examples (gmx-order-examples)
• GMX: GMX whitepaper (gmx-whitepaper)

Control Notes

1. Official domain

Official domain is the decision point where public documentation must become an operating rule. In this package, it means DEX onboarding starts by confirming the real GMX surface and docs. The practical action is to open only the official domain and docs before connecting a wallet. The unresolved edge is look-alike sites or sponsored search results, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

2. Connected chain

Connected chain is the decision point where public documentation must become an operating rule. In this package, it means available markets and account flows depend on the selected chain. The practical action is to record chain, wallet address and network before funding. The unresolved edge is whether a bridge or account abstraction path changes settlement, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

3. Funding route

Funding route is the decision point where public documentation must become an operating rule. In this package, it means wallet funds and account balances are operationally different. The practical action is to separate connected-wallet funds from GMX Account funds in notes. The unresolved edge is cross-chain deposit delay or failed bridge state, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

4. Delegated permission

Delegated permission is the decision point where public documentation must become an operating rule. In this package, it means subaccount or relay flows can introduce delegated authority. The practical action is to review delegated permission before enabling faster trading. The unresolved edge is who can revoke permission after device loss, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

5. Order preview

Order preview is the decision point where public documentation must become an operating rule. In this package, it means perpetual orders depend on collateral, leverage, fees and price impact. The practical action is to preview order parameters before signing. The unresolved edge is market movement between preview and execution, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

6. Exit path

Exit path is the decision point where public documentation must become an operating rule. In this package, it means safe onboarding includes withdrawal and permission cleanup. The practical action is to test small withdrawal and revoke unused approvals after learning. The unresolved edge is what happens if the interface, RPC or relay is unavailable, so the article keeps that edge explicit instead of turning it into a reward claim, licensing claim, approval claim, recovery guarantee, price implication, settlement guarantee or platform ranking.

The operating test is also narrow. A public page can prove public wording.

Known Unknowns

• look-alike sites or sponsored search results
• whether a bridge or account abstraction path changes settlement
• cross-chain deposit delay or failed bridge state
• who can revoke permission after device loss
• market movement between preview and execution
• what happens if the interface, RPC or relay is unavailable

Practical Takeaway

A GMX onboarding checklist should separate wallet connection, GMX Account funding, delegated trading and order execution before any user opens a position. GMX documentation describes SDK setup, frontend integration, delegated-trading contracts and order examples, while the GMX whitepaper frames the product as a decentralized perpetual exchange with wallet-based access. The useful tutorial outcome is to verify the official domain, connected chain, wallet balance versus GMX Account balance, delegated permission, order preview, collateral token, leverage setting, fees and withdrawal path before a user treats a successful connection as safe trading readiness. The article stops at the evidence boundary. It helps the reader decide what to inspect next without converting public documentation into a promise that a private account, wallet, callback, policy framework, settlement route or liquidity position will work under every future condition.