feat(perps): myx write integrations

[abretonc7s]

Description

Add MYX as the second perpetual futures provider alongside HyperLiquid. This PR implements all write operations (place/close/cancel/edit orders, TP/SL, margin adjustment) and completes the full provider integration using @myx-trade/sdk v1.0.6.

MYX is a permissionless perpetual futures DEX on BNB Chain (mainnet) and Linea Sepolia (testnet). All provider-specific logic is encapsulated in MYXProvider.ts, following the same AggregatedPerpsProvider architecture as HyperLiquid.

What's included

Core provider layer:

• MYXProvider -- 39 fully implemented PerpsProvider interface methods (market/limit orders, TP/SL, cancel, close, margin, batch operations)
• MYXClientService -- SDK wrapper for REST calls, auth, price polling, WebSocket klines
• MYXWalletService -- signing integration via MetaMask KeyringController
• myxAdapter -- SDK type to PerpsProvider type adapters
• myxConfig -- constants (fees, contracts, collateral config)

Key architectural decisions:

• On-chain transactions for every trade (vs HL's off-chain matching engine)
• REST polling (5s) for positions/orders/account (MYX WS doesn't push account data -- documented in tracker)
• Hybrid REST + WS for candle charts
• TP/SL implemented as separate trigger orders (vs HL's position-attached TP/SL)
• Broker revenue via referral rebate model (tagging done, activation pending MYX team)

Validation:

• 14 agentic recipes covering reads, market orders, position management, limit orders, and full lifecycle
• All 14 recipes passed 3-tier validation (PoC, CDP, human review)
• Full tracker: docs/perps/myx/MYX-INTEGRATION-TRACKER.md

Tests:

• 86% new code coverage (763/888 changed lines)
• 165 new tests across MYXProvider, MYXClientService, MYXWalletService, myxAdapter
• All existing tests fixed and passing

Changelog

CHANGELOG entry: null

Related issues

Fixes: TAT-2461, TAT-2462, TAT-2471, TAT-2472, TAT-2473, TAT-2474, TAT-2475, TAT-2477, TAT-2478, TAT-2508, TAT-2524, TAT-2531, TAT-2532, TAT-2533, TAT-2534, TAT-2580

Manual testing steps

Feature: MYX perpetual futures trading

  Scenario: user places a market order on MYX
    Given app is on testnet with MYX provider selected
    And wallet has sufficient USDC balance

    When user navigates to a MYX market (e.g. META)
    And presses Long
    And enters $110 order size
    And presses Place Order
    Then order is submitted on-chain
    And position appears in positions list after block confirmation (~10-15s)

  Scenario: user closes a position
    Given user has an open MYX position

    When user presses Close on the position
    And confirms the close
    Then position is removed after block confirmation

  Scenario: user sets TP/SL on a position
    Given user has an open MYX position

    When user presses Auto Close on the position
    And sets Take Profit and Stop Loss prices
    And presses Set
    Then TP/SL trigger orders are created
    And position shows TP/SL prices

  Scenario: user places and cancels a limit order
    Given app is on testnet with MYX provider selected

    When user places a limit order at a price below market
    Then order appears in open orders list
    When user cancels the order
    Then order is removed from open orders

Screenshots/Recordings

Before

N/A -- MYX provider did not exist before this PR.

After

01-read-markets.mp4

02-read-account.mp4

03-calculate-fees.mp4

04-validate-order.mp4

05-read-fills.mp4

06-place-market-order.mp4

07-update-tpsl.mp4

08-add-margin.mp4

09-close-position.mp4

10-place-and-close-all.mp4

11-place-limit-order.mp4

12-cancel-order.mp4

13-edit-order.mp4

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

High Risk
High risk because it adds on-chain MYX order execution/cancel/edit/close and margin/TP-SL flows, plus new validation and polling logic that directly affects trading correctness and user funds.

Overview
Adds full MYX write-path support in MYXProvider (place/edit/cancel/batch cancel/close/batch close, TP/SL trigger orders, and margin adjustment), including authenticated context setup, per-pool min order sizing with buffer, dynamic fee-rate fetching, and hybrid WS-triggered refresh + REST polling for orders/positions/account.

Expands MYX configuration (myxConfig) with network-specific collateral decimals/addresses, contract + explorer metadata, CAIP asset IDs, contract-price conversions, caching TTLs, and fee precision defaults; exports new API parsing helpers for MYX REST values.

Tightens order validation plumbing by returning minimumRequired from validateOrder through PerpsController/UI hooks, updates UI formatting/fallback displays (position size formatting, oracle price display fallback, market stats -- defaults), and adjusts close-position sizing semantics (treat full close as size: undefined).

^{Written by Cursor Bugbot for commit 287571e. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​myx-trade/​sdk@​0.1.265 ⏵ 1.0.6	+6		-3

View full report

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokePerps, SmokeWalletPlatform, SmokeConfirmations
• Selected Performance tags: @PerformancePreps
• Risk Level: high
• AI Confidence: 85%

click to see 🤖 AI reasoning details

E2E Test Selection:
This PR introduces a major MYX perpetuals trading integration with the following key changes:

1. MYX SDK major version bump (0.1.265 → 1.0.6): Breaking API changes requiring significant refactoring throughout the MYX provider and client service layers.

2. PerpsController.ts: Minor type enhancement - validateOrder return type now includes minimumRequired?: number to surface per-pool minimum order sizes to the UI.

3. MYXProvider.ts: Massive implementation - previously all trading operations (placeOrder, editOrder, cancelOrder, closePosition, closePositions, updatePositionTPSL, updateMargin, withdraw) were stubbed with MYX_NOT_SUPPORTED_ERROR. They are now fully implemented with the new SDK v1.0.6 API.

4. MYXClientService.ts: Major refactor - new authentication flow (walletClient-only auth, WS auth), new order write operations (createIncreaseOrder, createDecreaseOrder, cancelOrder, cancelOrders, updateOrderTpSl, adjustCollateral), new market data methods (getBaseDetail, getOraclePrice, getMarketDetail, getPoolLevelConfig, getUserTradingFeeRate), and WebSocket subscriptions for positions/orders.

5. myxAdapter.ts: Significant data transformation changes - corrected API size/collateral parsing (human-readable strings vs 18-decimal scaled integers), position PnL/liquidation price calculations, leverage from SDK runtime field.

6. myxConfig.ts: New constants, contract addresses, collateral token address change (mainnet USDT address updated), network-aware collateral decimals.

Tag Selection Rationale:

• SmokePerps: Primary tag - the existing perps-add-funds.spec.ts test exercises the Perps Add Funds flow. The PerpsController changes (validateOrder type, MYX provider implementation) must be validated. This is the most directly impacted test.
• SmokeWalletPlatform: Required by SmokePerps tag description - Perps is a section inside the Trending tab, and changes to Perps views affect Trending.
• SmokeConfirmations: Required by SmokePerps tag description - Add Funds deposits are on-chain transactions that go through the confirmation flow.

No other test suites are impacted - changes are isolated to the Perps feature area (MYX provider, PerpsController, Perps UI hooks). No changes to Engine initialization, navigation, shared modals, or other controller systems that would affect other test suites.

Performance Test Selection:
The MYX provider now implements real trading operations with parallel pool config fetching, market detail caching (60s TTL), WebSocket subscriptions for positions/orders, and oracle price polling. These additions could impact perps market loading, position management, and add funds flow performance. The @PerformancePreps tag covers perps market loading, position management, add funds flow, and order execution - all directly affected by this PR's changes.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
83.1% Coverage on New Code
1.3% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

✅ E2E Fixture Validation — Schema is up to date
17 value mismatches detected (expected — fixture represents an existing user).
View details