MUX Protocol (MCB): project purpose, mechanism and token context
This source-bound review separates what the available documents say about MUX Protocol from information that remains unverified. The distinction is especially important for contracts, live integrations, supply data and present availability. Statements remain attributed to their supporting record, and an unresolved field is left open instead of being completed from a generic project pattern.
Purpose in the reviewed sources
A primary point in the source record is: MUX is a decentralized perpetual-trading aggregator and liquidity protocol that routes positions across several underlying leveraged trading sources and offers pooled liquidity. YearBull uses this to identify the stated role of MUX Protocol, not to infer demand, financial backing or future performance. The scope is intentionally narrow so that the article does not turn an issuer description into an independent performance claim.
A second source-bound point concerns the operating model: The aggregator selects a suitable liquidity route for a trader's position; liquidity providers supply pool assets and protocol fees are shared with MUXLP and veMUX participants according to the documented model. The statement should be checked against the current interface and deployment because product rules and integrations can change. A current interface check is still necessary because documentation can outlive the implementation it originally described.
Mechanism described by the project
The mechanism record also includes this statement: Users lock MCB and/or MUX to receive veMUX, which provides governance power, protocol income and MUX rewards; MUX can also be vested into MCB. It helps explain the role of the asset or system without promising rewards, liquidity, revenue rights or governance powers beyond the cited scope. This protects the distinction between how a system is described and what a user can enforce or execute today.
For present-day identification, the evidence records: The official documentation lists an MCB supply cap of 4,803,144, including 3,803,144 current circulation and 1,000,000 reserved for future MUX vesting. MUX has a 1,000,000 supply cap and 1,000 daily emission, with vesting into MCB over one year. That description does not remove the need to verify the exact network, contract and supported interface. A matching name is not enough when different contracts or representations can trade under similar labels.
Supply and token context
For token structure, the record provides the following: MUX documentation states that trading fees are allocated among liquidity providers, veMUX holders and protocol-owned liquidity according to protocol version and fee type. Absent or qualified economic parameters remain open questions and should not be converted into current facts. Supply and allocation statements are treated as dated disclosures rather than permanent properties of the asset.
The source material further notes: MUX is a decentralized perpetual-trading aggregator and liquidity protocol that routes positions across several underlying leveraged trading sources and offers pooled liquidity. This is useful technical context, but permissions, counterparties, oracles, bridges, custody and withdrawal conditions still require operational review. Each dependency can change the practical risk even when the high-level project description remains the same.
Contracts, versions and interfaces
A final detail in this part of the record is: The aggregator selects a suitable liquidity route for a trader's position; liquidity providers supply pool assets and protocol fees are shared with MUXLP and veMUX participants according to the documented model. YearBull treats it as a source-bound claim and does not extend it into an investment conclusion. Where external confirmation is absent, the wording remains explicitly tied to the reviewed source record.
The dated evidence supports this narrow conclusion: Users lock MCB and/or MUX to receive veMUX, which provides governance power, protocol income and MUX rewards; MUX can also be vested into MCB. Because deployments evolve, it should be compared with the latest official record before use. A newer primary source should be used when it conflicts with this dated evidence or identifies a replacement deployment.
What the sources do not establish
The evidence establishes the following while leaving other fields open: The official documentation lists an MCB supply cap of 4,803,144, including 3,803,144 current circulation and 1,000,000 reserved for future MUX vesting. MUX has a 1,000,000 supply cap and 1,000 daily emission, with vesting into MCB over one year. Current activity and market conditions should not be inferred from that statement. The page can still provide a useful identity record without inventing a missing metric or operational status.
The record closes with this supported point: MUX documentation states that trading fees are allocated among liquidity providers, veMUX holders and protocol-owned liquidity according to protocol version and fee type. Before acting, users should reconcile it with current identity, contract, access and risk information. The exact checks depend on the asset, but a current primary source and full contract comparison are the minimum identity controls.
Key takeaways
- MUX is a decentralized perpetual-trading aggregator and liquidity protocol that routes positions across several underlying leveraged trading sources and offers pooled liquidity.
- The aggregator selects a suitable liquidity route for a trader's position; liquidity providers supply pool assets and protocol fees are shared with MUXLP and veMUX participants according to the documented model.
- Users lock MCB and/or MUX to receive veMUX, which provides governance power, protocol income and MUX rewards; MUX can also be vested into MCB.
- The official documentation lists an MCB supply cap of 4,803,144, including 3,803,144 current circulation and 1,000,000 reserved for future MUX vesting. MUX has a 1,000,000 supply cap and 1,000 daily emission, with vesting into MCB over one year.
- MUX documentation states that trading fees are allocated among liquidity providers, veMUX holders and protocol-owned liquidity according to protocol version and fee type.
YearBull Rank on this page
Current YearBull Rank for mcdex: #863.
Rank change (nearest points).
Reading rule: lower is better in this ranking.
- 7d window (2026-10-21): #2410 → #863 (up by 1547).
- 30d window (2026-09-28): #432 → #863 (down by 431).
YearBull Rank is a comparative index on YearBull that helps contextualize a coin’s position versus others over time. It is best read as relative context across time windows, not as a guarantee.
Liquidity posture: stable placement often correlates with stable participation. If the line drifts, liquidity may be gradually shifting.
Cycle framing: phase changes usually leave a footprint in consistency. If the line breaks range, confirm with more than one week.
Risk profile: short bursts do not always translate into durable placement. If the last week is quiet, the current rank is usually easier to trust.
Market structure: one venue can dominate the profile in short windows. If rank improves slowly, it often reflects broader access or steadier participation.
