{
  "schemaVersion": 1,
  "id": "mux",
  "version": "1.0.0",
  "name": "MUX",
  "reviewedAt": "2026-10-14",
  "reviewIntervalDays": 14,
  "reviewer": "Decentralised News editorial research",
  "evidenceType": "provider_documentation",
  "liveTested": false,
  "summary": "MUX is a suite, not one uniform execution venue. Aggregator routes can combine underlying protocols, while native V3 pools and leverage boosting introduce distinct collateral and cost conditions.",
  "scope": "Provider-documentation review of MUX perpetual trading. Not a live execution test, exhaustive product inventory, security audit or individual eligibility assessment.",
  "decisionTitle": "Inspect the route behind the unified trading screen.",
  "decisionContext": "Scope: MUX aggregator routing and native V3 documentation. V1 and Degen rules are not assumed to apply to every route. No live quote comparison or routing benchmark was performed.",
  "sources": [
    {
      "id": "routing",
      "name": "MUX perpetual aggregator",
      "url": "https://docs.mux.network/protocol/overview/leveraged-trading-aggregator",
      "reviewedAt": "2026-10-14"
    },
    {
      "id": "v3",
      "name": "MUX V3 trading protocol",
      "url": "https://docs.mux.network/protocol/overview/mux-v3-trading-protocol",
      "reviewedAt": "2026-10-14"
    },
    {
      "id": "fees",
      "name": "MUX fee structure",
      "url": "https://docs.mux.network/protocol/fee-structure",
      "reviewedAt": "2026-10-14"
    }
  ],
  "networks": [
    {
      "id": "mux",
      "name": "MUX perpetual trading (review scope)",
      "collaterals": [],
      "collateralNote": "V3 pools have different collateral and exposure configurations. Verify the actual pool or underlying protocol; there is no universal token list in this brief."
    }
  ],
  "claims": [
    {
      "id": "routing",
      "question": "Can one trade use multiple underlying venues?",
      "label": "Provider-reported",
      "finding": "The aggregator describes routing across one or more liquidity sources based on market, size, available liquidity, estimated costs and user preferences.",
      "consequence": "Inspect the selected sources. A single interface can expose the position to several protocols and their distinct constraints.",
      "sourceIds": [
        "routing"
      ]
    },
    {
      "id": "cost",
      "question": "Does the native fee schedule apply to every route?",
      "label": "Provider-reported",
      "finding": "The fee page explicitly says third-party routes adapt to the underlying protocol. Native V3 separately charges opening/closing position fees and hourly borrowing fees.",
      "consequence": "Price the chosen route and holding period. A native headline rate cannot establish the cost of a routed position.",
      "sourceIds": [
        "fees"
      ]
    },
    {
      "id": "boost",
      "question": "Is leverage boosting free additional margin?",
      "label": "Provider-reported",
      "finding": "The aggregator guide describes additional supplied margin, opening/closing boost charges and a separate boost-funding charge alongside underlying funding.",
      "consequence": "Include both layers of charges when boosting applies. More available leverage is not evidence of a safer position.",
      "sourceIds": [
        "routing"
      ]
    },
    {
      "id": "collateral",
      "question": "Do all V3 pools accept the same assets?",
      "label": "Provider-reported",
      "finding": "The V3 guide describes pools with different collateral, markets and directional exposure. Positions can route to multiple elemental pools.",
      "consequence": "Confirm the actual pool configuration rather than treating a broad collateral category as universally accepted.",
      "sourceIds": [
        "v3"
      ]
    },
    {
      "id": "modes",
      "question": "Does a V3 feature description establish every route setting?",
      "label": "Provider-reported",
      "finding": "The native V3 overview lists cross and isolated margin. Aggregator routes can use other underlying protocols.",
      "consequence": "Verify the margin mode on the selected route; do not transfer native V3 settings to another venue.",
      "sourceIds": [
        "v3",
        "routing"
      ]
    },
    {
      "id": "measured",
      "question": "Has DN verified the lowest-cost routing claim?",
      "label": "Not measured",
      "finding": "No contemporaneous multi-venue execution benchmark, withdrawal test or stop-loss reliability test was conducted for this brief.",
      "consequence": "Treat optimization statements as provider claims. Documentation alone cannot support a cheapest-platform ranking.",
      "sourceIds": [
        "routing"
      ]
    }
  ],
  "illustration": null,
  "unknowns": [
    "Current executable quotes and all-in holding costs",
    "Independent fill, stop-loss and withdrawal reliability",
    "Live signing permissions and revocation behaviour",
    "Individual eligibility and current regional restrictions"
  ],
  "history": [
    {
      "date": "2026-10-14",
      "type": "DN publication",
      "detail": "Initial documentation brief. Account-specific conditions and evidence limits are preserved in this version."
    }
  ],
  "reviewTriggers": [
    "Changed official product, fee or margin documentation",
    "A substantiated correction",
    "The 14-day editorial review deadline"
  ],
  "disclosure": "DN may receive compensation through commercial links elsewhere on the site. This brief contains no trading CTA or payout-based ranking. A documentation review does not establish current operational status or user eligibility."
}