mux.network valid
MUX Protocol
MUX Protocol is a decentralized perpetual trading aggregator and exchange deployed on Arbitrum, BNB Chain, Avalanche and Optimism. MUX routes leveraged trading positions across multiple on-chain perpetual venues to minimize composite trading cost, and operates its own zero-price-impact perpetual exchange powered by the MUXLP pool and MUX3LP pools. The protocol is non-custodial, governed by MCB token holders, and supports up to 100x leverage.
- Authority
- 47 reach 6 · trust 5 · quality 21 · freshness 15
- Tier
- listed
- llms.txt
- https://mux.network/llms.txt
- Sections
- 6
- Links
- 26
- Size
- 10149 bytes
- Popularity rank
- #777558
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T17:58:45.338Z
- Last checked
- 2026-10-26T01:52:00.972Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T01:51:55.294Z. Cached copy · Source on mux.network
# MUX Protocol
> MUX Protocol is a decentralized perpetual trading aggregator and exchange deployed on Arbitrum, BNB Chain, Avalanche and Optimism. MUX routes leveraged trading positions across multiple on-chain perpetual venues to minimize composite trading cost, and operates its own zero-price-impact perpetual exchange powered by the MUXLP pool and MUX3LP pools. The protocol is non-custodial, governed by MCB token holders, and supports up to 100x leverage.
MUX is a suite of protocols, not a single product. The suite consists of the **MUX Perpetual Aggregator** (routes positions to the best-cost venue across integrated perp DEXes), the **MUX V3 Trading Protocol** (zero-price-impact perpetual exchange against the MUX3LP pools and highly customizable exposure options for LPs), the **MUX V1 Trading Protocol** (zero-price-impact perpetual exchange against the MUXLP pool), and the **MUX Degen Protocol** (long-tail perpetual markets via the DegenLP pool). Arbitrum is the primary chain.
The aggregator compares composite trading costs across integrated protocols — including price, spread, slippage, price impact, position fees, max leverage, maintenance margin, and liquidation fees — then selects the optimal route. When needed, MUX supplies additional margin to boost leverage beyond what the underlying venue offers natively (leverage boosting). Each aggregated position is isolated in its own smart contract (position container). Cross-chain aggregation allows positions to be opened on a different chain than the trader's funds, using MUX's universal liquidity mechanism.
The native trading protocol uses a dark oracle (a private price oracle aggregating feeds from multiple exchanges) to fill orders with zero price impact and near-zero toxic arbitrage. Liquidity is unified across all deployed chains through a broker module that monitors total cross-chain pool depth.
**Token ecosystem:** MCB is the main token. veMUX is vote-escrowed MCB used for governance voting and earning protocol income (distributed as ETH). MUXLP is the liquidity provider token representing shares of the native trading pool. MUX3LP tokens are the liquidity provider token of the MUX V3 pools. The MUX token is an escrowed reward token convertible to MCB.
For product mechanics, trading rules, fees, liquidation logic, tokenomics, and contract addresses, the authoritative source is https://docs.mux.network/ — prefer it over homepage copy or social posts.
## Core Product
- [MUX Trading App](https://app.mux.network/): Primary interface for perpetual trading with aggregated routing, position management, and liquidity actions. Supports wallet connection, order placement, and real-time position tracking.
- [MUX Homepage](https://mux.network/): Public entry point with protocol overview, ecosystem links, and product navigation.
- [MUX Stats Dashboard](https://stats.mux.network/public/dashboard/13f401da-31b4-4d35-8529-bb62ca408de8): Public analytics dashboard showing protocol volume, TVL, fee
…Machine-readable: GET /v1/resolve?q=mux.network · GET /v1/domain/mux.network · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage mux.network, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for mux.network:
1. POST https://agentwebmap.com/v1/sites/mux.network/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://mux.network/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/mux.network/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/mux.network).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.