MUX Protocol (MCB)

Overview

MUX Protocol is a decentralized platform for trading perpetual contracts. A perpetual contract lets a trader take a position on an asset’s price without buying the asset itself. Unlike a standard futures contract, it has no set expiration date. MUX brings several trading venues together in one interface and can route a position to a suitable source of liquidity. The protocol also operates its own pools, which give traders another place to open positions. (docs.mux.network)

MCB is MUX Protocol’s main token. Its central use is in the protocol’s staking system: holders can lock MCB to receive veMUX, which is tied to governance participation and a share of protocol income. MCB has a different role from MUX, the project’s reward token, and from the tokens issued to liquidity providers. (docs.mux.network)

History & Team

From MCDEX to MUX

The project grew out of MCDEX, an earlier decentralized perpetual-trading platform. Liu Jie identified himself as MCDEX’s founder in a paper describing its trading design. Jean, another co-founder, described the team’s interest in using smart contracts to build a platform for derivatives trading. (wikibitimg.fx994.com)

The move to the MUX name came with a broader product design. Rather than relying only on its own trading pool, the team built an aggregator that could connect traders to other perpetual protocols. MUX launched its aggregator in December 2022 with routes that included its native trading system and GMX. It later added gTrade, expanding the kinds of markets available through the interface. Development now covers both the aggregator and MUX’s own trading protocols. (medium.com)

Technology & How It Works

Routing a perpetual trade

When a trader opens a position, the MUX aggregator looks at which connected protocols support the market and have room for the trade. It compares costs such as fees, spread, slippage, and price impact, along with factors that affect leverage and liquidation. It can send an order to one venue or divide a larger position among several. The trader then manages the combined position through MUX’s interface. (docs.mux.network)

A position container is a smart contract that holds an individual trader’s routed position. It interacts with the underlying trading venue on that trader’s behalf. MUX also describes a leverage-boosting feature: for some routed trades, its pool can supply additional margin, changing the position’s leverage and liquidation threshold. The protocol advertises leverage of up to 100 times for supported trades. (docs.mux.network)

Native pools and pricing

MUX’s own protocols use liquidity supplied to pools. Its earlier MUXLP pool holds a portfolio of assets that can support trades across deployed networks. A broker module tracks available capacity across those networks, so a trade on one chain can make use of the system’s shared liquidity calculation without moving every pooled asset for each order. Pricing for this design uses the project’s “dark oracle,” which draws on exchange price feeds and is intended to limit trading ahead of orders. (docs.mux.network)

The newer MUX V3 design uses separate elemental pools. Each can support chosen collateral and market exposures, including a selected long or short side. The aggregator can route a trade to one or more of these pools. This gives liquidity providers more control over which markets their assets support than a single shared portfolio would. (docs.mux.network)

Tokenomics & Utility

Four tokens, four roles

MUX documents four tokens in its economic model:

• MCB is the main token that holders can lock.
• MUX is a non-transferable reward token. It can be locked or vested into MCB.
• veMUX represents a time-weighted stake used in the governance and income-sharing model.
• MUXLP represents a share of the earlier native liquidity pool.

V3 elemental pools use their own MUX3LP liquidity-provider tokens. MUX3LP and MUXLP describe interests in different pool designs; neither serves the same purpose as MCB. (docs.mux.network)

The documented MCB supply cap is 4,803,144 tokens. Of that amount, 1,000,000 is reserved for MUX rewards that may vest into MCB over one year. A change to the cap requires a governance proposal and a time delay under the project’s stated rules. MCB or MUX can be locked for periods from two weeks to four years. Longer locks receive more veMUX per token, linking a holder’s stake to the length of the commitment. (docs.mux.network)

veMUX holders receive allocations of protocol income and MUX rewards under the documented incentive rules. Liquidity-provider income is allocated through the pool systems. The protocol also sets aside part of its income for protocol-owned liquidity—assets the protocol holds in its own pool to support trading. (docs.mux.network)

Ecosystem & Use Cases

Trading, liquidity, and governance

MUX serves three main groups. Traders use it to open and manage perpetual positions across connected venues. Liquidity providers supply assets to native pools and receive pool tokens that reflect their participation. MCB holders can lock tokens for veMUX to take part in the project’s governance model and income allocation. (docs.mux.network)

The aggregator’s documented integrations include GMX V1, GMX V2, gTrade, and MUX’s own trading protocols. These connections matter because each venue can offer different markets and trading terms. Through its gTrade integration, MUX has also supported routed positions in markets such as foreign exchange, indices, and commodities. In the native V3 system, liquidity providers can choose pools with different collateral assets and market exposure, allowing more tailored strategies. (docs.mux.network)

Advantages & Challenges

MUX’s main advantage is convenience: its aggregator compares connected venues and presents routed positions through one interface. Splitting an order can draw on more than one source of liquidity. Its own pools add another route, while V3 gives liquidity providers a choice of market and collateral exposure. These features bring several parts of perpetual trading together without requiring traders to select every underlying venue themselves. (docs.mux.network)

That design also brings complexity. Traders need to understand perpetual contracts, margin, and the terms of the venue that fills a position. Token holders face a separate set of rules for MCB, MUX, veMUX, and liquidity-pool tokens. The protocol’s documentation says its oracle and broker functions operate through an off-chain multiplexing layer, while its governance process currently relies on forum discussion and a DAO multisignature wallet. These arrangements are important to how the system works and how changes are made. (docs.mux.network)

Where to Buy & Wallets

MCB is available through 1inch on Arbitrum, as listed in MUX’s token documentation. That documentation identifies the MCB contract address on both Arbitrum and Ethereum as 0x4e352cF164E64ADCBad318C3a1e222E9EBa4Ce42. MCB also exists on BNB Chain. Staking and reward distribution take place on Arbitrum, so the network holding the token matters for that use. (docs.mux.network)

MetaMask can hold MCB on supported networks, including Arbitrum and Ethereum. A holder can add MCB as a custom token using its contract address if the balance does not appear automatically. The wallet’s selected network must match the network on which the tokens are held. (support.metamask.io)

Regulatory & Compliance

MUX’s terms restrict access to its site and interface for U.S. persons and people in listed prohibited locations. The terms also address sanctions and require access to comply with applicable laws. In the United Kingdom, Financial Conduct Authority rules prohibit regulated firms from marketing, distributing, or selling covered cryptoasset derivatives to retail clients. These rules concern derivatives access; the treatment of a token such as MCB is a separate legal question. (mux.network)

MUX’s leveraged perpetual-trading model does not align with widely used Shariah standards for conventional derivatives. The Accounting and Auditing Organization for Islamic Financial Institutions states that conventional futures contracts are not permitted under its standards, and it sets limits on excessive uncertainty, known as gharar. Because MCB’s staking utility is linked to income from the protocol’s trading activity, that connection is relevant when considering the token under those principles. (aaoifi.com)

Future Outlook

MUX’s development plans center on improving the trading routes and native pool system. Its documentation describes further integrations for the aggregator and V3 portfolio pools designed to combine elemental pool tokens in an automatically rebalanced portfolio. It also describes a longer-term goal of decentralizing the off-chain oracle and broker functions. For governance, the stated plan is to add veMUX voting in phases as the protocol develops. These plans show where the team intends to extend the system, while the existing aggregator and pool designs remain its foundation. (docs.mux.network)

Summary

MUX Protocol combines a perpetual-trading aggregator with its own liquidity pools. Its MCB token connects holders to the staking and governance model through veMUX, while separate tokens handle rewards and liquidity provision. The project’s place in decentralized finance rests on making fragmented perpetual markets easier to access and giving pool participants more choice in how they supply liquidity. (docs.mux.network)