MYX Finance Explained: Matching Pools, Perpetuals and LP Risk
MYX Finance is a decentralised perpetual exchange built around what it calls a Matching Pool Mechanism, or MPM. Instead of maintaining a conventional order book, the system matches long and short exposure while a liquidity pool temporarily takes the unmatched side.
The mechanism is promoted as providing zero-slippage execution at an oracle price. Traders should read that phrase narrowly: it describes the protocol’s quoted execution model, not an absence of fees, price risk, liquidation risk or limits during stressed markets.
Key takeaways
Long and short positions can offset each other, reducing the amount of liquidity-provider capital actively exposed.
When the market is imbalanced, the pool becomes the counterparty and can gain or lose as traders’ positions change.
Oracle-priced execution can remove price impact at entry while adding dependence on oracle accuracy, keepers and contract logic.
High leverage can turn a small market move, funding cost or execution delay into a substantial loss.
How the Matching Pool Mechanism works
Orders that increase long exposure and orders that increase short exposure can be matched economically. When one side dominates, the pair-specific liquidity pool takes a passive opposing position so the trade can open immediately. Later orders in the opposite direction can reduce that imbalance and release pool capital.
Funding payments are intended to encourage balance between long and short open interest. A balanced market uses less pool capital for active counterparty exposure; an imbalanced market makes the liquidity provider more sensitive to trader profit and loss.
What “zero slippage” means here
MYX documentation describes trades executed using oracle prices. This differs from submitting a large swap against an AMM curve, where the trade itself moves the quoted price. A user still pays trading, funding and network costs and may face restrictions on position size or new orders when available pool capacity is exhausted.
Oracle failure, delayed updates or incorrect keeper execution can create losses even if the interface shows no traditional price impact. The precise contracts and current product version matter because the platform also describes newer permissionless-market and vault products.
Why automatic deleveraging exists
If profitable open positions become too large relative to available pool capital, the protocol may use automatic deleveraging to close selected profitable positions and reduce open interest. This protects system solvency but means a profitable position can be reduced before the trader chooses to close it.
Due-diligence checklist
Confirm the current product version, network and canonical contracts.
Review supported collateral, leverage limits, fees and funding calculations.
Identify the oracle, keeper dependencies and response to stale prices.
Understand liquidation and automatic-deleveraging rules.
For liquidity provision, model a persistent long or short imbalance.
Check audits, upgrade powers, incident history and withdrawal conditions.
Derivatives products need precise communication because a simple phrase such as “zero slippage” can hide the risks users actually need to understand. Crynet supports technical Web3 content and go-to-market strategy grounded in verifiable product mechanics.