GMX Venue Profile Draft: Liquidity Pools, Oracles, and Collateral Risk

Risk Questions Before Mechanics

A GMX review should begin with the risks created by pooled liquidity, oracle-priced execution, and market conditions that can change faster than static documentation.

• Which assets back the liquidity pool, and how could pool imbalance affect traders and liquidity providers?
• How are index prices sourced, updated, and protected during volatility or thin market conditions?
• What liquidation, borrowing, funding, and withdrawal rules must be rechecked before any article leaves draft status?

Mechanics To Document Neutrally

The profile should describe oracle-priced execution, collateral handling, fees, funding or borrowing costs, pool utilization, and withdrawal paths without comparing GMX as better or worse than another venue.

Reviewer Source Notes

Before publication, record the documentation date, the exact product areas reviewed, unresolved source gaps, and any stale assumptions. If current parameters cannot be confirmed locally, leave the uncertainty visible.

• Manual source review placeholder: Record the protocol docs, app screens, and parameter pages checked with review dates.
• Reviewer note template: Summarize current assumption, source gap, affected section, and reviewer initials before publication.
• Publication blocker log: Keep unresolved oracle, liquidity pool, collateral, fee, or withdrawal questions visible in the draft.