# Overview MUX is a protocol suite that offers the 1st decentralized perpetual trading aggregator and the P2Multi-Pool model; it provides traders with deep aggregated liquidity, optimized trading cost, up to 100x leverage, diverse market options and unique aggregator features like smart position routing, aggregated position, leverage boosting and liquidation price optimization. The MUX Perpetual Aggregator has integrated with leading perps liquidity sources like MUX V3 Trading Protocol, MUX V1 Trading Protocol, MUX V1 Degen Protocol, GMX V1, GMX V2, gTrade and will continue to integrate with more protocols. **Key components in the MUX Protocol Suite:** * MUX Perpetual Aggregator - A decentralized sub-protocol in the MUX protocol suite that automatically selects the most suitable liquidity route and minimizes the composite cost for traders while meeting the needs of opening positions. The aggregator can also supply additional margins for traders to optimize liquidation prices and raise the leverage to 100x on aggregated underlying protocols. * MUX V3 Trading Protocol - A decentralized perpetual trading protocol in the MUX protocol suite that offers 0% price impact trading, up to 100x leverage, cross & isolated margin modes, no counterparty risks and a multi-pool setup that allows LPs to supply liquidity with highly customizable risk exposure options. Traders will trade against the MUX V3 elemental pools (MEP) through the MUX P2Multi-Pool model. * MUX V1 Trading Protocol - A decentralized perpetual trading protocol MUX protocol suite that offers 0% price impact trading, up to 100x leverage, no counterparty risks for traders and an optimized on-chain trading experience. Traders will trade against the MUX V1 native pool (MUXLP) on the MUX V1 Trading Protocol. * MUX V1 Degen Protocol - A decentralized perpetual trading protocol MUX protocol suite designed based on the MUX V1 trading protocol but tailored for enhancing long-tail assets trading experiences. Traders will trade against the MUX DegenLP pool on the MUX V1 Degen Protocol. The MUX protocol suite will expand as the dev contributors continuously develop new features and integrations to meet traders' needs. # MUX V3 Trading Protocol Since launching MUX V1 in August 2022 and witnessing $48B+ trading volume by September 2024, the organic user adoption and trading volume from MUX V1 and the Perpetual Aggregator (MUX V2) have proven the oracle-based P2Pool model's product-market fit for on-chain perpetual trading. Using the oracle-based model, MUX can offer fast order execution speed and a much lower spread than the traditional order-book-based trading platforms. However, the existing P2Pool model has limitations, like relatively low capital efficiency and limited market diversity. MUX V3 introduces a redesigned liquidity setup and new trading features to improve LP performances and trading experiences. **MUX V3 Trading Features:** * 0% price impact & spread for bluechip markets * Up to 100x leverage * Cross Margin & Isolated Margin Modes * 1-Click trading with a chargeable trading account (Coming Soon) * New price aggregation powered by Chainlink Data Streams and the MUX Dark Oracle * Enhanced aggregator trading experience with more aggregated liquidity sources **MUX V3 Liquidity Setup:** * P2Multi-Pool * MUX V3 offers a new multi-pool liquidity setup (P2Multi-Pool) to meet diverse risk-exposure preferences from LPs. * The liquidity pools from the P2Multi-Pool setup are MUX V3 pools (MUX3LP). * Each MUX V3 pool supports different collateral, market exposure and long/short exposure options. * Supported collateral options include stablecoins, yield-bearing tokens, volatile assets and liquidity re-staking tokens. * Trader’s positions will be automatically routed to one or more MUX V3 elemental pools through the MUX Aggregator to support the needed size while ensuring optimized trading cost. * LPs will earn fees paid by traders. * Highly customizable market and long/short-exposure options * Under the V3 pools, each supported market has separated long and short exposure, without pursuing mandatory long-short balance. * The market determines the long-short ratio of each trading pair under the elemental pools. * LPs can supply liquidity based on their preferences through highly customizable markets and long/short-exposure options. * For any given direction of a trading pair (e.g., longing BTC), the liquidity can be provided by multiple pools with different collateral assets. * Each MUX V3 pool can also provide liquidity to multiple trading pairs. * High capital efficiency * High market diversity # MUX Perpetual Aggregator ## Motivation Perpetual trading is one of the fastest growing domains in DeFi. Currently, more than 20 perpetual trading protocols are deployed on various blockchains. However, as the protocols proliferate at a rapid pace, obstacles start to appear along the way: 1. The liquidity is scattered on different protocols, leading to liquidity underutilization. 2. While the liquidity is fragmented on different chains, there isn’t a native approach to utilize the cross-chain liquidity. 3. The differences between pricing mechanisms and margin parameters on each protocol are vast; traders can’t easily access the optimal pricing and trading experiences. The MUX protocol aims to provide the best-in-class trading experiences for traders. Therefore, to resolve the mentioned issues surrounding perpetual trading protocols, the MUX protocol launched the MUX Leveraged Perpetual Aggregator, a sub-protocol in the MUX protocol suite. ## Mechanisms ### Smart Position Routing MUX Perpetual Aggregator automatically routes traders' positions to one or multiple liquidity sources based on market, available liquidity, position size, composite trading cost and user preferences. **Market:** Traders' positions will only route to suited integrated protocols that offer the required market. **Available Liquidity & Position Size:** Traders' positions will route to one or multiple suited integrated protocols that offer sufficient available liquidity to support the needed position size. **Composite Trading Cost:** The MUX Aggregator will dynamically compare composite trading costs offered by all integrated trading protocols and select the most cost-effective route/routes for traders. Unlike spot trading, the "trading cost" of leveraged trading is a composite factor containing the price, spread, slippage, price impact, position fees and other potential explicit trading costs. In addition, the composite factor also involves implicit costs like max leverage, maintenance margin, liquidation fees, available liquidity, etc. The MUX protocol comprehensively compares the trading cost of the aggregated protocols. As a result, it selects the most suitable liquidity route and minimizes the composite cost for traders while meeting the needs of opening positions. **User Preference:** All available liquidity sources can be turned on/off under trading settings; if a liquidity source is turned off, the trader's position won't be routed to that protocol. ### Leverage Boosting & Liquidation Price Optimization Every underlying leveraged trading protocol usually requires different Initial Margin and Maintenance Margin. The differences lead to the variation of max open leverage and maintenance leverage on these protocols. Additionally, protocols with deep liquidity on the market might not offer the ideal max leverage to meet traders’ needs. To provide optimal trading experiences and leverage options, when the MUX Aggregator opens positions on the underlying leveraged protocol on behalf of the traders, it can supply additional margin for traders to raise the leverage and lower the MM requirements. This feature can help boost the max leverage and optimize liquidation price for traders. Suppose the required initial margin rate on the underlying protocol is *IM*, the maintenance margin rate is *MM*, then the max open leverage is *1/IM*, and the max maintenance leverage is \_1/MM. \_When a trader wishes to open a position with a larger leverage L (L > 1/IM), then the trader only needs to provide a margin with the amount of *1/LSize and MUX Aggregator will provide an additional margin with the amount of Size \* (MM - MM2). \_The additional margin comes from the MUX Universal Liquidity Pool. In addition, the MUX protocol offers another maintenance margin rate (MM2), which is usually lower. When the position’s remaining margin gets lower than \_MM2Size*, the position will be liquidated, and the corresponding position on the underlying protocol will also be closed. When position opening and closing take place, the MUX Aggregator charges a minimal fee, which is the leverage boost fee based on the supplied additional margin. *BoostFee = (MM - MM2) \* Size \* BoostFeeRate*. When liquidation occurs, the position will settle with the liquidation price; the remaining margin will be returned to the traders after the liquidation fee charged by the underlying protocol and boost fee are deducted. When traders open positions through MUX Aggregator, the underlying protocol will charge funding fees from traders. Since the MUX Aggregator supplies additional margin for traders, it will also charge a specific boost funding fee for traders every 1 hour. \_BoostFundingFee=BoostMargin*FundingRate=(MM - MM2) \* Size* FundingRate. \_Similar to how funding is handled on the MUX protocol, the underlying protocol funding fee and boost funding fee will be deducted from the traders’ collateral. Also, if the position open time hasn’t reached 1 hour upon the funding collection time, the boost funding will round up to 1 hour; if a position is closed before the next funding collection time, no boost funding will be charged. **Example** On GMX V1, the position fee rate is 0.1%, IM is 2%, and MM is 1%. On MUX, suppose the MM is 0.5%, BoostFeeRate is 2%. When a trader tries to open a $10,000 position using 100x leverage, the trader only needs to use a margin of *10000/100=$100*; the MUX protocol will supply the additional margin of *(1% - 0.5%) \* $10000 = $50*. In addition, the trader also needs to pay the GMX position open fee of *$10000\*0.1%=$10* and the MUX leverage boost fee of *$50\*2%=$1*. If the trader’s position is in a loss due to price fluctuation, the position will be liquidated when the remaining margin is below *$10000\*0.5% = $50*. If the liquidation on GMX doesn’t have slippage, the trader needs to pay the GMX position fee of *$10000\*0.1%=$10* and MUX leverage boost fee of *$50\*2%=$1*; the remaining *$50-$10-$1=$39* margin will be returned to the trader. ### Aggregated Position & Split Orders MUX allows traders to open and manage aggregated positions with components routed to multiple liquidity sources. This feature can help to support large position sizes and lower overall trading costs for opening large positions. For example, if integrated protocols A, B and C on the MUX Aggregator each have $30M available liquidity for ETH long positions, when a trader tries to open an $80M ETH long position, the MUX aggregator will split the trader's position into three orders to these three protocols in one trade; the estimated trading cost will determine each protocol's position ratio. MUX will preferably route trades' positions to liquidity sources with the lowest estimated total trading cost. ### Liquidity Aggregation When specific underlying liquidity protocols can’t meet the position needs of traders, the MUX Aggregator can aggregate the scattered liquidity from different protocols, further offering a consistent and convenient trading experience. Traders won’t need to be distracted by the liquidity supplier behind the Aggregator; they only need to focus on the unified trading interface. For example, let’s say a user opens a $100M position through the MUX Aggregator. Within this aggregated position, $50M is on protocol A, $30M is on protocol B, and $20M is on protocol C. The obstacle to liquidity aggregation is the potential pricing differences in various protocols, and the MUX protocol can’t simply merge positions with different entry prices. To address this issue, the MUX Aggregator will use the following approaches: 1. Deeply collaborate with underlying leveraged trading protocols and acquire their guaranteed accurate pricing. 2. The MUX Aggregator can bear the underlying protocol pricing differences under a specific range, then offer traders unified pricing. ### Position Container The MUX Aggregator Protocol manages a set of smart contracts for holding traders’ positions. These contracts are called the “position containers”. When a trader opens a position through MUX Aggregator, the Aggregator will create a position container, then use it to open the position on the underlying leveraged trading protocol on behalf of the trader. From the underlying protocol’s perspective, the position container contract is its direct user. In addition, the MUX Aggregator provides an API for inquiring about the traders’ addresses behind their position containers. Each position possesses a separate position container. The containers furthest isolate risks among the users, which is fundamental for ensuring the safety of the MUX protocol. ## Roadmap The MUX Aggregator sub-protocol is an essential component of the MUX protocol suite. The MUX dev contributors will continuously develop and deliver features to meet traders’ needs. * MUX Protocol V2: Composite with GMX and offer 100x leverage for traders * MUX Protocol V3: Launch the cross-chain aggregation feature * MUX Protocol V4: The integrated management of underlying positions # MUX V1 Trading Protocol MUX native trading protcol is a decentralized perpetual trading protocol offering zero price impact trading, up to 100x leverage, self-custody, aggregated liquidity and an optimized on-chain trading experience. In addition, MUX is the first multi-chain native protocol unifying pooled liquidity across deployed chains to maximize capital efficiency. **Traders can use MUX to:** * Open up to 100x leveraged positions with zero price impact * Trade with optimal cost * Trade with aggregated liquidity * Use multiple types of assets as collateral **Liquidity providers can use MUX to:** * Supply liquidity and obtain MUXLP tokens * Stake MUXLP to earn protocol income and MUX token rewards For income and rewards allocation, please check [Incentives](https://github.com/mux-world/references/blob/main/INCENTIVES.md#protocol-income-allocation). **Community members can use MUX to:** * Lock MCB to receive veMUX * Hold veMUX to earn protocol income and MUX token rewards. MUX Native Trading Protocol is currently deployed on Arbitrum, BNB Chain, Avalanche, Optimism and will expand to more networks in the future ## Mechanisms MUX Naive Trading Protocol core features are supported by three unique mechanisms: * [Universal Liquidity](#universal-liquidity) * [Multi-Asset Pool](#multi-asset-pool) * [Dark Oracle](#dark-oracle) ### Universal Liquidity Liquidity pools on trading protocols are usually fragmented from chain to chain, leading to inconsistent liquidity depths. MUX unifies liquidity across networks by using a broker module, which is a bot that monitors total liquidity and the liquidity reserved for margin trading. After a trader places an order, the broker will calculate the available liquidity across deployed networks and fill the order if it can meet position size. The universal liquidity mechanism offers higher capital efficiency on all deployed networks without moving pooled assets around. Let’s assume the pools on Arbitrum, Avalanche, BSC and Fantom each hold 10 ETH, and 5 ETH are currently reserved for active positions. As the broker observes all deployed networks, it will determine the total universal liquidity as 40 ETH, and the available liquidity as 35 ETH. If a trader places a 20 ETH long order on Arbitrum, the following process will take place: 1. After the order is submitted on the chain, the broker proceeds to deal with it. 2. The broker will check if the universal liquidity meets the order size requirements. * Total universal liquidity is 40 ETH (10 + 10 + 10 + 10), and the available universal liquidity is 35 ETH (40 - 5) * 35 ETH is greater than the order’s required 20 ETH and as such the broker will proceed to fill the order 3. The broker will fill the order with the ETH price obtained from the [dark oracle](#dark-oracle). Consequently, the trader will hold a 20 ETH long position. After opening this long position, the 20 ETH will be reserved until the position is closed. On the LP side, after LPs supply ETH on Avalanche, BSC or Fantom, trading activities on Arbitrum can utilize these ETH without actually moving them. In the rare cases when the pooled liquidity on a chain can’t fully cover traders’ profits, the traders will receive [muxTokens](/tutorials/redeem) as profits. After receiving muxTokens, users can redeem them into related tokens on other chains. For example, if the pool on Arbitrum only holds 10 ETH while a trader tries to withdraw 20 ETH profits from a related position on this chain, the trader will receive 10 ETH and 10 muxETH. Meanwhile, the pool on Avalanche has 50 ETH, so the trader can bridge the 10 muxETH to Avalanche, then redeem them into 10 ETH. MUX protocol deploys the broker on the [Multiplexing Layer](/protocol/multiplexing-layer) to enable universal liquidity. Liquidity-related metrics can be seen on the [MUX Statistics](https://app.mux.network/metabase/public/dashboard/e1134798-4660-489f-a45a-45d9adb05918) page. ### Multi-Asset Pool The MUXLP pool, which is the counterparty of traders, is always fully collateralized with a [portfolio](/protocol/liquidity#muxlp-pool-portfolio) of blue-chip assets and stablecoins. When traders open leveraged positions, the pool will reserve required assets until the position is closed; meanwhile, the pool will hold positions against traders in the opposite direction. If a trader's position is in profit, upon closure, the trader can withdraw the collateral and profits from the reserved assets. If the trader's position is at a loss, upon closure, traders will pay for the losses with the collateral. For risk management, long and short positions under each market will have open interest caps. The caps won't exceed pooled liquidity capacity, so the pool is always capable of paying for the trader's profits; therefore, the traders don't have counterparty risks. Let's assume 1 ETH is priced at $1000, the MUXLP pool has 4 ETH, and a trader uses 1000 USDC as collateral to open a 3x ETH long position. In this trade, the MUXLP pool reserves 3 ETH (worth $3000) for the trader. Meanwhile, the pool holds a 3 ETH (worth $3000) spot position. At this moment, the MUXLP pool's net exposure is 1 ETH. ETH price then rises to $2000, and the USD value of this position becomes $6000; the unrealized profits are $3000. The trader now closes this position and can withdraw the 1000 USDC collateral and 1.5 ETH (worth $3000) from the reserved ETH as profits. In this example, the pool loses 1.5 ETH from this trade, but the USD value of pooled ETH remains unchanged since 1.5 ETH is now worth $3000. When it comes to long positions, the MUXLP pool can suffer Coin-denominated losses but remains delta neutral. When traders open short positions, the MUXLP pool will reserve stablecoins for traders. In this case, the pool is exposed to USD-denominated losses. However, since there are open interest caps under each market, the pool will always manage the capacity at a level where all trader's profits can be fully covered. Also, the market is usually skewed; the total open interest of longs is greater than shorts in most circumstances, so the MUXLP pool mostly holds net short positions, which are less than the assets in the pool. ### Dark Oracle MUX uses a dark oracle that aggregates price feeds from multiple exchange sources, including Binance, to ensure pricing accuracy and stability. A dark oracle is a private price oracle which does not publicly display the prices of assets in the pool, and the primary purpose is to prevent front-running. In addition, the dark oracle eliminates nearly all room for toxic arbitrage, further enabling zero price impact trading. When traders place orders, the MUX broker module will obtain prices from the dark oracle and fill the orders with zero price impact. MUX protocol deploys the dark oracle on the [Multiplexing Layer](/protocol/multiplexing-layer). # MUX V1 Degen Protocol MUX Degen Protocol is a decentralized perpetual trading protocol tailored to enhance the long-tail assets trading experience. The protocol uses dynamic price impact to adjust trading prices based on the position size; the deployed mechanism will mitigate price manipulation risks and ensure a fairer and more stable trading experience for all participants. The MUX Degen Protocol has its own liquidity pool: the DegenLP pool. Traders will trade against the DegenLP pool on the MUX Degen Protocol. Due to the high-risk exposure, the DegenLP pool will only be open to whitelisted sophisticated traders and LPs to supply liquidity. # Liquidity ## MUX V3 Trading Protocol MUX V3 offers a new multi-pool liquidity setup (P2Multi-Pool) to meet diverse risk-exposure preferences from LPs. LPs can supply liquidity based on their preferences through highly customizable collateral, market exposure and long/short-exposure options. ### MUX V3 Pools (MUX3LP) The liquidity pools from the P2Multi-Pool setup are MUX V3 elemental pools (MUX3LP). Each MUX V3 elemental pool supports different collateral, market exposure and long/short exposure options. Supported collateral options include stablecoins, yield-bearing tokens, volatile assets and liquidity re-staking tokens. Trader’s positions will be automatically routed to one or more MUX V3 elemental pools through the MUX Aggregator to support the needed size while ensuring optimized trading cost. LPs will earn fees paid by traders. Under the elemental pools, each supported market has separated long and short exposure, without pursuing mandatory long-short balance. The market determines the long-short ratio of each trading pair under the elemental pools. For any given direction of a trading pair (e.g., longing BTC), the liquidity can be provided by multiple pools with different collateral assets. Each MUX V3 elemental pool can also provide liquidity to multiple trading pairs. ### Buy/Sell MUX3LP LPs can supply liquidity to MUX V3 by buying MUX3LP tokens using the supported collateral token from the preferred MUX V3 pool. ### Holding MUX3LP Tokens After buying MUX3LP tokens, the earned fees will be directly reflected in the MUX3LP token price. LPs don’t need to claim the fees separately. Traders’ PNL and the price movements of the collateral token will also affect the MUX3LP token price. Since each V3 Pool has only one collateral option and separated market and long/short exposures, LPs can supply liquidity while running external hedging to reach precisely neutral exposure. ### MUX V3 Portfolio Pools (Coming Soon) MUX V3 offers auto-rebalancing MUX3LP token portfolio pools for LPs seeking diverse portfolio strategies and exposure options. The V3 Portfolio Pools can be seen as the “V3 MUXLP.” Each portfolio pool consists of multiple MUX3LP tokens with a target weight. LPs can buy MUX3LP tokens and then supply them to the portfolio pool; the portfolio pools will automatically re-balance the MUX3LP tokens based on the target weight. The MUX V3 portfolio pools are built on top of Balancer V3. The MUX3LP tokens from the portfolio pools are supplied to Balancer V3. ### MUX3LP Profits & Risks **MUX3LP Profits Sources:** * Position open & close fees * Position borrowing fees * Liquidation fees * MUX token rewards **MUX3LP Risks** * Since the MUX V3 elemental pools are the counterparty of traders, MUX3LP has positions holding related risks and can suffer losses. * Pooled collateral token price drawback. ## MUX V1 Trading Protocol The universal liquidity pool on MUX holds a portfolio of assets, and each asset has a targeted weight in the pool. Pooled assets will be utilized for MUX margin trading to earn fees. Users can provide liquidity by buying MUXLP with assets allowed by the portfolio. MUXLP tokens are minted when buy orders are filled and burnt when sold. The MUXLP token price is calculated by dividing the MUXLP pool value by the total MUXLP supply. After buying MUXLP tokens, users can stake the tokens to earn protocol income and MUX rewards. Liquidity-related metrics can be seen on the [MUX Statistics](https://stats.mux.network/public/dashboard/e1134798-4660-489f-a45a-45d9adb05918). ### Buy / Sell MUXLP Users can buy MUXLP tokens on all deployed networks with assets allowed by the portfolio. [Buy / Sell MUXLP Tutorial](/tutorials/provide-liquidity#buy-muxlp) After placing a buy or sell MUXLP order, it takes an extended pending time (currently set as 18 minutes) for the order to be filled. The pending time serves two purposes: * Prevent potential arbitraging that can harm LP * Since the MUXLP pool holds a portfolio of assets and allows users to buy MUXLP with any supported assets, there is potential arbitrage room if front-runners execute quick buy and sell orders with different assets. The pending time can help to eliminate this room for arbitrage. * Ensure the protocol can correctly calculate the universal liquidity across four networks * The MUX protocol needs to consider different network latency and finalization times when calculating the universal liquidity; the pending time helps ensure correct calculation and proper token allocation for MUXLP buyers and sellers. ### MUXLP Staking After buying MUXLP tokens, users can stake them on Arbitrum to earn protocol income and MUX rewards. Please check the [incentives](https://github.com/mux-world/references/blob/main/INCENTIVES.md) section for detailed rewards distribution formulas. [MUXLP Staking Tutorial](/tutorials/stake#stake-muxlp) ### MUXLP Pool Portfolio The MUXLP pool holds a portfolio of blue-chip assets and stablecoins, each having a targeted weight in the pool. When the asset weight moves above or below its target, the fees for buying or selling MUXLP with this asset will adjust accordingly. * If the weight is below target, buying MUXLP with this asset requires lower fees; selling MUXLP into this asset requires higher fees. * If the weight is above target, buying MUXLP with this asset requires higher fees; selling MUXLP into this asset requires lower fees. Liquidity composition, weight and multiplexing statistics can be seen on the [MUX Liquidity](https://app.mux.network/#/liquidity/stats?chainId=42161) page. ### MUXLP Profits & Risks **MUXLP Profits Sources:** * A portion of the protocol fees * Funding payments * Liquidation penalties * MUX token rewards **MUXLP Risks** * Since the MUXLP pool is the counterparty of traders, MUXLP has positions holding related risks and can suffer losses * Pooled assets price drawback ### Protocol-Owned Liquidity (POL) Sufficient liquidity is crucial for trading protocols, as deeper pools can support higher open interest. However, acquiring and maintaining liquidity can be costly and unstable if solely reliant on liquidity providers (LP). Therefore, instead of “renting” all liquidity from external sources, the MUX protocol implements the POL mechanism to become gradually self-sufficient. The MUXLP pool consists of liquidity from two sources, LP and POL. Upon genesis, the protocol purchased MUXLP tokens with funds raised from previous rounds; also, 15% of protocol income will go to POL. POL is the base of the MUXLP pool and will grow sustainably with cumulative trading volume. The proportion of POL in the total liquidity is protocol owned ratio (POR.) Furthermore, if someday the POL is sufficient enough, the proportion of the income distributed to the LP might be reduced. ## MUX V1 Degen Protocol The MUX Degen Protocol has its own liquidity pool: the DegenLP pool. Traders will trade against the DegenLP pool on the MUX Degen Protocol. The DegenLP pool is stablecoin-only. Due to the high-risk exposure, the DegenLP pool will only be open to whitelisted sophisticated traders and LPs to supply liquidity. # Tokenomics The protocol’s tokenomics involves four tokens: * [MCB](#mcb) * [MUX](#mux) * [veMUX](#vemux) * [MUXLP](#muxlp) ![](/files/7XhKPC9z55Yssw3gxWI1) ## MCB MCB is the protocol’s main token. Users can lock MCB to receive veMUX which entitles them to protocol income and MUX rewards. #### Supply MCB token supply cap: 4,803,144 * 3,803,144 MCB tokens are from the current circulation. * 1,000,000 MCB tokens are reserved for future MUX vesting. * Users can vest MUX tokens into MCB over 1 year. Please check the [MUX](#mux) section for more details. The supply cap won’t change unless a governance proposal for increasing the cap is initiated and passed. If the supply cap is voted to increase, the change should take effect after a 14-day time lock. #### Locked-Staking Users can lock MCB and / or MUX to obtain veMUX, period from 2 weeks to 4 years. The locked-staking is time-weighted, so longer time locks will be allocated with more distributed veMUX. * 1 MCB or MUX locked for 2 weeks = 0.009589 veMUX * 1 MCB or MUX locked for 1 month = 0.020548 veMUX * 1 MCB or MUX locked for 1 year = 0.25 veMUX * 1 MCB or MUX locked for 4 years = 1 veMUX [Locked-Staking Tutorials](/tutorials/stake#vemux-locked-staking) #### Token Address * Arbitrum: [0x4e352cF164E64ADCBad318C3a1e222E9EBa4Ce42](https://arbiscan.io/token/0x4e352cF164E64ADCBad318C3a1e222E9EBa4Ce42) * Ethereum: [0x4e352cF164E64ADCBad318C3a1e222E9EBa4Ce42](https://etherscan.io/token/0x4e352cF164E64ADCBad318C3a1e222E9EBa4Ce42) #### You can buy MCB tokens from * [1inch (Arbitrum)](https://app.1inch.io/#/42161/classic/swap/ETH/MCB) #### Bridge MCB tokens are available on Arbitrum, BNB Chain and Ethereum. Since staking activities and rewards distribution will all take place on Arbitrum, it is recommended to bridge your MCB tokens to Arbitrum. Recommended bridges for MCB: * [cBridge](https://cbridge.celer.network/#/transfer) * [Arbitrum Official Bridge](https://bridge.arbitrum.io/) ## MUX MUX is the protocol’s non-transferable reward token. Users can earn MUX through holding veMUX or staking MUXLP. #### Utility MUX tokens can be utilized in two different options: stake MUX to obtain veMUX, or vest MUX into MCB. The current supply cap for MUX is 1,000,000, and the daily emission is 1,000. The supply of MUX tokens will decrease if they are vested into MCB; the vesting process will take one year. The MUX supply won’t increase unless a related governance proposal is initiated and passed. If the supply cap is voted to increase, the change should take effect after a 14-day time lock. #### Locked-Staking The locked-staking rules and rewards distribution for staked MUX are identical with staked MCB. [Locked-Staking Tutorials](/tutorials/stake#vemux-locked-staking) #### Vesting Vest MUX to MCB tokens linearly over one year. Two channels are available for vesting: * Quota channel: Vest MUX allowed by the quota, which is correlated with veMUX. The quota increases as veMUX generates new MUX and decreases as MUX converts into MCB. * Capacity channel: Vest MUX allowed by capacity, which is determined by users’ reserved MUXLP tokens. The capacity will not change as long as users’ reserved MUXLP tokens remain staked. [MUX Vesting Tutorials](https://github.com/mux-world/references/blob/main/STAK.md#vest-mux) #### Token Address Arbitrum: [0x8BB2Ac0DCF1E86550534cEE5E9C8DED4269b679B](https://arbiscan.io/token/0x8BB2Ac0DCF1E86550534cEE5E9C8DED4269b679B) MUX tokens are non-transferable and only available on Arbitrum. ## veMUX veMUX is the protocol governance token; with more veMUX comes more voting power on protocol governance. Users can obtain veMUX from locking MCB and / or MUX. Holding veMUX will grant users protocol income and MUX rewards. veMUX tokens are minted when users lock MCB and / or MUX and will be burnt as the lock time decreases. veMUX tokens are non-transferable and only available on Arbitrum. #### Rewards The protocol income collected from trading fees will be allocated to veMUX holders; please check the [Incentives](broken://pages/6ieve53b62fhiLcmovYW) section for details. ## MUXLP MUXLP is the protocol’s liquidity provider token, which users can buy with assets allowed by the pool [portfolio](/protocol/liquidity#muxlp-pool-portfolio). After buying the tokens, users can stake them to earn protocol income and MUX rewards. Please check the [Liquidity](/protocol/liquidity) section for more detailed information. #### MUXLP Staking [Buy & Sell MUXLP Tutorial](/tutorials/provide-liquidity#buy-muxlp) [MUXLP Staking Tutorial](/tutorials/stake#stake-MUXLP) #### Rewards The protocol income collected from trading fees will be allocated to MUXLP stakers; please check the [Incentives](broken://pages/6ieve53b62fhiLcmovYW) section for details. #### Supply There is no supply cap for MUXLP tokens. MUXLP tokens are minted when buy orders are filled, and burnt when sold. #### Token Address * Arbitrum: [0x7CbaF5a14D953fF896E5B3312031515c858737C8](https://arbiscan.io/token/0x7CbaF5a14D953fF896E5B3312031515c858737C8) * BNB Chain: [0x07145Ad7C7351c6FE86b6B841fC9Bed74eb475A7](https://www.bscscan.com/token/0x07145Ad7C7351c6FE86b6B841fC9Bed74eb475A7) * Avalanche: [0xAf2D365e668bAaFEdcFd256c0FBbe519e594E390](https://snowtrace.io/token/0xaf2d365e668baafedcfd256c0fbbe519e594e390) * Fantom: [0xDDAde9a8dA4851960DFcff1AE4A18EE75C39eDD2](https://ftmscan.com/token/0xDDAde9a8dA4851960DFcff1AE4A18EE75C39eDD2) **Bridge** You can buy MUXLP tokens on Arbitrum, BNB Chain, Avalanche and Fantom. MUXLP staking and rewards distribution are only available on Arbitrum. Recommended bridge for MUXLP: * [cBridge](https://cbridge.celer.network/#/transfer) # Income Allocation veMUX holders, MUX3LP holders and MUXLP stakers can earn protocol income and MUX rewards. ## MUX V3 & V1 Trading Protocol Income Allocation ### Protocol Income Allocation The native protocol income collected from trading fees will be allocated as follows: `Total Protocol Income × (85% × POR + 15%)`: Allocate for veMUX holders (in ETH) * POR is the rate of [Protocol Owned Liquidity](/protocol/liquidity#protocol-owned-liquidity) `V3 Trading Protocol Income × 85% × (1 - POR)`: Allocate for MUX3LP holders `V1 Trading Protocol Income × 85% × (1 - POR)`: Allocate for MUXLP stakers (in ETH) ### Integrated Protocol Referral Rebates Allocation 100% of the referral rebates MUX Aggregator earns from integrated protocols will be allocated to veMUX holders. ### MUX Rewards Allocation 1,000 MUX will be distributed to veMUX holders and MUXLP stakers daily, allocated as follows: `1000 × (1-veRate) × (1-POR)`: Allocate for MUXLP stakers * veRate is the MCB and MUX staking ratio * veRate = veMUX Total Supply / (MCB Circulating Supply + MUX Circulating Supply) The rest will be allocated for veMUX holders ### Income & Rewards Distribution Time Weekly rewards (ETH and MUX) for veMUX are distributed at the end of every epoch. Therefore, you can see and claim all rewards from the previous epoch on Thursdays UTC. ETH rewards for MUXLP staking are gradually distributed after your first epoch. MUX rewards for MUXLP staking are gradually distributed after you start staking. Epochs start and end weekly on Thursdays UTC. ## MUX V1 Degen Protocol Income Allocation The DegenLP pool protocol income will be allocated as follows: `DegenLP Pool Income × 85%`: Allocate for veMUX holders (in ETH) * DegenLP Pool × 15%: Purchase DegenLP and add to the DegenLP pool After the DegenLP pool is open for more whitelisted LPs, the whitelisted LP income will be allocated as follows: `Whitelisted LP Income × 70%`: Allocate for Whitelisted LPs (in USDC) `Whitelisted LP Income × 30%`: Allocate for DegenLP pool protocol income * DegenLP Pool Income × 85%: Allocate for veMUX holders (in ETH) * DegenLP Pool × 15%: Purchase DegenLP and add to the DegenLP pool # Referral Program With the MUX referral program, referrers can earn rebates from referee’s trading fees, and traders (referees) can enjoy trading fee discounts by using a referral code. In the referral tier system, everyone starts with a casual tier with no threshold, and users can level up the tier by increasing the veMUX holding. The referral rebate rate goes up to 35%, and the trading fee discount goes up to 10%. | Tier | veMUX Holding (USD) | Your Rebate Rate | Referee's Discount | | ------ | ------------------- | ---------------- | ------------------ | | Casual | ≥ $0 | 2.5% | 2.5% | | VIP 1 | ≥ $5K | 5% | 5% | | VIP 2 | ≥ $50K | 10% | 5% | | VIP 3 | ≥ $250K | 20% | 5% | | VIP 4 | ≥ $500K | 25% | 5% | | 💎🙌 | ≥ $1M | 35% | 10% | The referral rebates and trading fee discounts are derived from leveraged trading position open and close fees; the open and close fee rates are 0.075% of the position size. Additionally, the rebates and discounts don’t apply to the spread on BNB, AVAX and FTM positions. The value of an account’s veMUX holding at Thursday 0:00am UTC determines the account’s referral tier for the previous week. When the MUX protocol calculates users’ veMUX holding value, it uses the MCB token average price from the past seven days. Regarding trading fee discounts, traders can apply referral codes to their accounts; the trading fees will be discounted based on the rate of the code. The referral rebates and trading fee discount will airdrop to users’ recipient addresses weekly on Thursday UTC, in the form of WETH tokens. ## Referral Tutorials * [As Referrer - Create a Referral Code](/tutorials/referral#as-referrer-create-referral-code) * [As Referrer - Share Referral URL](/tutorials/referral#as-referrer-share-referral-url) * [As Referrer - Change Code Recipient Address](/tutorials/referral#code-details-change-code-recipient-address) * [As Referrer - Transfer Referral Code Ownership](/tutorials/referral#code-details-transfer-referral-code-ownership) * [As Trader - Apply a New Referral Code](/tutorials/referral#as-trader-apply-a-new-referral-code) * [As Trader - Change Applied Referral Code](/tutorials/referral#as-trader-change-applied-referral-code) # Fee Structure The following fee structure applies to MUX V1 and MUX V3 trading protocols. If a trader's position routes to a third-party underlying leveraged trading protocol through the MUX aggregator, the fee structure will adapt accordingly. Please check the [Aggregator](/protocol/overview/leveraged-trading-aggregator) section and related underlying protocol docs for more details. ## MUX V3 Trading Protocol ### Position Fee The MUX protocol charges position fees when traders open and close positions. The position fee is fixed at 0.06% and calculated as follows: * Open Fee: 0.06% × Asset Price × Position Size * Close Fee: 0.06% × Asset Price × Position Size The collected position fees are allocated to MUX3LP holders, veMUX holders, and POL. Please check [Protocol Income Allocation](/protocol/income-allocation) for more details. ### Borrowing Fees MUX V3 Trading Protocol charges borrowing fees after traders borrow pooled assets for positions. The borrowing fees are collected every 1 hour. Borrowing fees for long and short positions are calculated separately on MUX. borrowingFeeRate = max{utilization × limitRate, baseRate} baseRate (Annualized) * Long - ETH: 8% * Long - BTC: 8% * Long - ARB: 8% * Long - BNB: 8% * Long - AVAX: 8% * Long - FTM: 8% * Short: 8% limitRate (Annualized) * Long - ETH: 40% * Long - BTC: 40% * Long - ARB: 40% * Long - BNB: 40% * Long - AVAX: 40% * Long - FTM: 40% * Short: 50% Utilization calculation examples: * ETH utilization = global long ETH position / ETH in pool * Short utilization = global short position / Stablecoins in pool The collected borrowing fees are allocated between MUX3LP holders, veMUX holders and POL, the same as the collected position fee allocated. The baseRate and limitRate might change in the future as the MUX dev contributors make continuous evaluations. ### Liquidation Fee The maintenance margin (MM) on the MUX protocol is 0.5%, and the liquidation fee is 0.06%. Therefore, a 0.06% (if it exists) margin will be collected as the fee when a position is liquidated. The remaining margin after liquidation will return to traders. The liquidation fee will be shared between external MUX3LP holders, veMUX holders and POL, the same as the collected position fee allocated. ## MUX V1 Trading Protocol ### Position Fee The MUX protocol charges position fees when traders open and close positions. The position fee is fixed at 0.06% and calculated as follows: * Open Fee: 0.06% × Asset Price × Position Size * Close Fee: 0.06% × Asset Price × Position Size The collected position fees are allocated to MUXLP stakers, veMUX holders and POL. Please check [Protocol Income Allocation](/protocol/income-allocation) for more details. ### Funding Payments After traders borrow pooled assets for positions, the MUX protocol charges funding payments, which can be seen as borrowing fees from positions. The funding payment is collected every 1 hour. Long and short positions funding are calculated separately on MUX. fundingFeeRate = max{utilization × limitRate, baseRate} baseRate (Annualized) * Long - ETH: 8% * Long - BTC: 8% * Long - ARB: 8% * Long - BNB: 8% * Long - AVAX: 8% * Long - FTM: 8% * Short: 8% limitRate (Annualized) * Long - ETH: 40% * Long - BTC: 40% * Long - ARB: 40% * Long - BNB: 40% * Long - AVAX: 40% * Long - FTM: 40% * Short: 50% Utilization calculation examples: * ETH utilization = global long ETH position / ETH in pool * Short utilization = global short position / Stablecoins in pool The collected funding fees are allocated between external MUXLP stakers, veMUX holders and POL, the same as the collected position fee allocated. The baseRate and limitRate might change in the future as the MUX dev contributors makes continuous evaluations. ### Liquidation Fee The maintenance margin (MM) on the MUX protocol is 0.5%, and the liquidation fee is 0.06%. Therefore, 0.06% (if it exists) margin will be collected as the fee when a position is liquidated. The remaining margin after liquidation will return to traders. The liquidation fee will be shared between external MUXLP stakers, veMUX holders and POL, the same as the collected position fee allocated. ### Spread MUX V1 offers 0% spreads under the ETH and BTC market. The spreads under BNB, AVAX and FTM markets are fixed. * ETH: 0% * BTC: 0% * ARB: 0.075% * BNB: 0.12% * FTM: 0.12% * AVAX: 0.15% ## MUX V1 Degen Protocol ### Position Fee The MUX Degen protocol charges position fees when traders open and close positions. The position fee is fixed at 0.032% and calculated as follows: * Open Fee: 0.032% × Asset Price × Position Size * Close Fee: 0.032% × Asset Price × Position Size The collected position fees are allocated between LPs, veMUX holders and the DegenLP Pool. Please check Protocol Income Allocation for more details. ### Borrowing Fee The MUX Degen protocol charges borrowing fees for the pooled liquidity reserved for traders’ long or short positions. Both long and short positions will always be charged for borrowing fees despite the skew. The borrowing fee will be charged from the position’s collateral every hour. The borrowing rate is fixed at 5% of the position size annually. The collected borrowing fees are allocated between LPs, veMUX holders and the DegenLP Pool. Please check Protocol Income Allocation for more details. ### Funding Fee After traders reserve pooled assets for positions, the MUX Degen Protocol charges funding payments from positions on the skewed side. The funding payment is collected every 1 hour. The funding fee rate for the less skewed side is 0%; the funding fee rate for the skewed side will be up to 50% annually. `fundingRateAPY = max(abs(longs - shorts) / α * β, β)` * When the skew is 0, the funding rate APY is 0; when the skew is α, the funding rate APY is β The collected funding fees are allocated between LPs, veMUX holders and the DegenLP Pool. Please check Protocol Income Allocation for more details. ### Price Impact The MUX Degen Protocol uses dynamic price impact to adjust trading prices based on the position size; the deployed mechanism will mitigate price manipulation risks and ensure a fairer and more stable trading experience for all participants. The price impact will always be positive. # Liquidation The following liquidation rules only apply to trading against the MUX native pool (MUXLP pool). If a trader's position routes to a third-party underlying leveraged trading protocol through the MUX aggregator, the liquidation rules will adapt accordingly. Please check the [Aggregator](/protocol/overview/leveraged-trading-aggregator) section and related underlying protocol docs for more details. ## Liquidation Under MUXLP Pool The maintenance margin is the minimum margin required to keep the position open and not liquidated. The position will be liquidated if its margin falls below the maintenance margin; when the position leverage rises, the likelihood of being affected by MM increases. Maintenance leverage is the maximum effective leverage that the position leverage can reach. The position will be liquidated if its leverage exceeds the maintenance leverage. Maintenance Margin (MM) = IndexPrice \* Position Value \* MMR% * Maintenance Margin Rate (MMR%) = 0.5% Maintenance Leverage = 1 / MMR% The liquidation fee on the MUX protocol is 0.1%. Therefore, 0.1% (if it exists) margin will be collected as the fee when a position is liquidated. The remaining margin after liquidation will return to traders. # Multiplexing Layer Two essential modules of the protocol, the dark oracle and broker module, are currently deployed on the multiplexing layer. These two modules are used to achieve zero price impact trading, universal liquidity and liquidity multiplexing. While most MUX protocol components are decentralized, the multiplexing layer infrastructures are currently off-chain. Balancing decentralization and product performance have been in continuous exploration during the development of MUX; the protocol needs to minimize trust in all aspects, but it also faces limitations from on-chain infrastructures. For example, existing on-chain oracles capture index prices at a relatively low frequency, leading to room for toxic arbitrage and lower pricing accuracy for margin trading. Also, no existing decentralized infrastructures provide a convenient interface for application protocol (like MUX) to effectively monitor and manipulate liquidity across chains. To achieve needed critical features, the MUX dev contributors built the multiplexing layer infrastructures from scratch and planned to decentralize them progressively. #### Next Phase After the protocol reaches a stable and self-sufficient state, we’ll start to decentralize the multiplexing layer. Depending on third-party infrastructure capabilities, the multiplexing layer can be decentralized in two directions. 1. If third-party decentralized infrastructures are improved and start to meet the performance requirements from MUX, the dev contributors will shift to using these decentralized services. 2. Suppose third-party decentralized infrastructures can’t meet the performance requirements in the foreseeable future. In that case, the MUX dev contributors will start to devise a light-weight decentralized network, which is governed and operated by veMUX holders, to provide the oracle and broker services. # Governance Currently, the MUX protocol governance process involves forum proposals and community discussions. Any proposed modifications to the protocol will be openly discussed on the forum, and the dev contributors will execute each proposal under the premise of shared opinions. The executions will be transparent, and the MUX dev contributors will notify the community through various channels before the implementation occurs. Except for an emergency protocol pause that prevents security incidents, all protocol modifications will only take effect after a 48-hour timelock; the delay would give community members a time window to take needed actions. After the protocol reaches a self-sufficient state (supported by [POL](/protocol/liquidity#protocol-owned-liquidity-pol)), veMUX voting will be added to the governance process. The voting process will initiate when the community comes to a rough consensus on a proposal. The decentralization of protocol governance needs to be phased due to development prioritization. Upon protocol launch, the highest priority is to ensure positive performances and efficient adaptation to the ever-changing market. Leading the governance allows the MUX dev contributors to implement constant improvements faster, further helping the protocol build a steady POL foundation. When the protocol reaches a broad user base and can stably provide optimized experiences for all trades, elevating the degree of decentralization will be the new priority. Voting will be progressively introduced to the governance process, starting from major protocol updates polling, then expanding to comprehensive protocol modifications. In future phases, trust will be minimized as veMUX holders are onboard to govern and shape the protocol into a better state. ## MUX Protocol Governance Scope MUX DAO multi-sig currently governs the MUX protocol smart contracts, and the scope includes general operation, maintenance and emergency actions. The governance involves two types of permission: time lock required and non-required. For general operation actions, time locks are required; all the proposed changes will only take effect after a 48-hour time lock. Maintenance actions won't affect protocol core features, so that they won't need a time lock. Emergency actions can take effect immediately and won't require time locks; these actions can potentially occur during security incidents or other events that can severely damage LPs and traders. Please check the detailed list below for all general operation, maintenance and emergency actions. ### General Operation #### LiquidityPool * Upgrade this smart contract * Transfer / Renounce owner (the TimeLock smart contract) * Add new type of assets to the pool * Set underlying asset symbol string * Set underlying asset initial margin rate * Set underlying asset maintenance margin rate * Set underlying asset open / close fee rate * Set underlying asset minimum profit limit * Set liquidity asset weight * Set base funding rate * Set dynamic funding rate * Set the address of on-chain oracle * Set fee rate for adding / removing liquidity * Set gas rebate rate * Set the dampener range of the stablecoin's price * Set funding payment collection time interval * Set who can execute emergency functions (who can skip the TimeLock) * Delegate ARB voting power in the LiquidityPool to MUX Protocol #### OrderBook * Upgrade this smart contract * Transfer / Renounce owner (the TimeLock smart contract) * Add rebalancer * Remove rebalancer * Set add / remove liquidity lock time * Set order overtime limit * Set who can execute emergency functions (who can skip the TimeLock) #### LiquidityManager * Upgrade this smart contract * Transfer / Renounce owner (the TimeLock smart contract) * Set vault smart contract address * Set pool smart contract address * Set handler (broker) * Configure slippage for adding liquidity on DEXes * Pause DEX mining mining interface adapter * Add / remove universal plug-in smart contract (bridging, etc） * Transfer owner (the TimeLock smart contract) * Renounce owner (the TimeLock smart contract) * Set maintainer address (maintainer can execute assets bridging) * Set allowed assets for bridging along with their targeted networks * Bridge assets using cBridge * Directly withdraw assets (for manual bridging) * Directly withdraw assets and assign targeted receiver (for manual bridging) #### NativeUnwrapper * Set ETH unwrap smart contract whitelist * Transfer / Renounce owner (the TimeLock smart contract) #### TimeLock * Upgrade this smart contract * Manage pre-minted mux tokens * Transfer / Renounce owner (the DAO multi-sign) * Set proposers * Set executors #### Vault * Upgrade this smart contract * Transfer / Renounce maintainer (the DAO multi-sign) ### Maintenance #### Vault * Collect and distribute protocol fees **LiquidityManager** * Transfer liquidity tokens among blockchains through whitelisted bridges **LiquidityPool** * Set MUXLP token price protection range ### Emergency #### LiquidityPool * Enable / disable trading of specific assets * Enable / disable using specific assets as underlying assets * Enable / disable using specific assets for opening positions * Enable / disable using specific assets for shorting * Enable / disable taking profits with stablecoin when trading specific assets * Enable / disable specific assets to be considered as stablecoin * Enable / disable using specific assets for adding liquidity * Set trading price spread * Set underlying asset maximum open interest cap #### OrderBook * Pause fill position & liquidity orders (the orders to pause during broker maintenance) * Add broker * Remove broker # Online Issues Here are some common errors you might encounter when using MUX. When the error details are one of the listed below, please follow the instructions on how to resolve these issues. If the following scenarios don’t cover your error details, please go to [MUX Discord](https://discord.com/invite/bd88NrzN3N) to open a ticket and report the issue. MUX community contributors will help to address the problems as soon as they can. ## Internal JSON-RPC error When your transactions fail to process due to the “Internal JSON-RPC error, the RPC used in your wallet is causing the issue. To address the issue, using Arbitrum as an example, you can go to Wallet Settings > Networks > Arbitrum > Change “New RPC URL.” You can use as a reference and try different listed RPC URLs until your transaction can be processed. ![](/files/NIOCpbchAjxIRYd0U4uJ) If you trade on DEXes frequently, it’s recommended to use high-performance RPC from or for a stabler experience. ## {} When the error details is empty, it’s usually indicating RPC issue as well. Please follow the Internal JSON-RPC error fix on how to address this issue. ## Max fee per gas less than block base fee This issue is caused by the gas fee limit you set in the wallet being too low. Please try to increase the gas limit and try the transaction again. ![](/files/24JsfwA2dJqhtS9cibft) ## Insufficient {symbol} balance, unable to pay gas This error means you currently have insufficient gas in your wallet to process any transactions. Please transfer more gas tokens (like $ETH on Arbitrum) to your address and then proceed with the transaction. ## gains pre check failed, enough liquidity for xxx amount, available liquidity xxx This error means Gains liquidity becomes insufficient to support your position after placing the order. Please try lowering the position size and then open the position again. # Audit * MUX V3 Trading Protocol contracts have been audited by [Guardian](https://guardianaudits.com/). Please check [here](https://github.com/mux-world/mux3-protocol/blob/main/audit/MUX%203%20Protocol%20Report.pdf) * MUX Leveraged Trading Aggreator contracts have been audited by [SolidProof](https://solidproof.io/). Please check [here](https://github.com/mux-world/mux-protocol/blob/main/audit/SolidProof-Audit-20221215.pdf) for the full report. * MUX V1 Trading Protocol contracts have been audited by [Certik](https://www.certik.com/). Please check [here](https://www.certik.com/projects/mux-protocol) for the full report. # Contracts * [DAO Multi-sig](/protocol/contracts/contracts-dao) * [MUX V3 Protocol Contracts](/protocol/contracts/contracts-mux3) * [MUX Leveraged Trading Protocol Contracts](/protocol/contracts/contracts-protocol) * [MUX Leveraged Trading Aggregator Contracts](/protocol/contracts/contracts-aggregator) * [MUX Degen Protocol Contracts](/protocol/contracts/contracts-degen) * [MUXLP Tranches Contracts](/protocol/contracts/contracts-tranches) # DAO Multi-sig DAO uses a multi-sig on each chain, and each multi-sig requires the confirmation of 4 out of 8 owners. ## Multi-sig Addresses | Chain Name | Address | | ------------ | -------------------------------------------------------------------------------------------------------------------------------- | | Arbitrum One | [0x029A4A97e892e7270d9B3B90bFEF95599BC6BfD6](https://arbiscan.io/address/0x029A4A97e892e7270d9B3B90bFEF95599BC6BfD6) | | Avalanche | [0x8564C77261094Abeee6d60a26d40f8DBAF23Fc94](https://snowtrace.io/address/0x8564C77261094Abeee6d60a26d40f8DBAF23Fc94) | | BNB Chain | [0xf67D9eC4F3362589E56AB0DBEe448EB7A4964204](https://bscscan.com/address/0xf67D9eC4F3362589E56AB0DBEe448EB7A4964204) | | Fantom | [0x55214EcCC18E0763B8F6cEE71C25be0ceD7a9FB6](https://ftmscan.com/address/0x55214EcCC18E0763B8F6cEE71C25be0ceD7a9FB6) | | Optimism | [0x7C8126ef43c09C22bf0CcdF7426180e6c48068A5](https://optimistic.etherscan.io/address/0x7C8126ef43c09C22bf0CcdF7426180e6c48068A5) | ## Multi-sig Owners | Owner Address | | ------------------------------------------ | | 0xa199BeD592FBdEbAa66674351Ae45d5Fd9103452 | | 0x73c5955dbB7a667e05da5fE7b8798c0fd4cE8E16 | | 0xee858B965820F6a648C1816F2B0925d44C5dB1F0 | | 0xB6ad7e26aFc71Bb00dEea47FEF069443DD09A622 | | 0x08483fDB868A072B344A2eCB7f8Ea0DC9f77e3dD | | 0xA851eE692b77C7bdf19EA7AC1e8aDe227c73CB45 | | 0x95F29832d4cABD348c66a6CAF0755b8b89F3e35C | | 0x55d21E661645Fa43dD82A9e283FEdbAABbf55fA9 | # MUX V3 Protocol Contracts | Contract Name | Upgradeable | Proxy Address | Implementation Address | | ----------------------------------------------------------------------------------------------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | [Mux3](https://github.com/mux-world/mux3-protocol/blob/main/contracts/core/Mux3.sol) | yes | [0x85c8F4a67F4f9AD7b38e875c8FeDE7F4c878bFAc](https://arbiscan.io/address/0x85c8F4a67F4f9AD7b38e875c8FeDE7F4c878bFAc) | [FacetMux3Owner](https://github.com/mux-world/mux3-protocol/blob/main/contracts/core/owner/FacetMux3Owner.sol): [0x52162C310565868E76d60b3E1Fc69cc4C0aD5189](https://arbiscan.io/address/0x52162C310565868E76d60b3E1Fc69cc4C0aD5189) | | | | | [FacetManagement](https://github.com/mux-world/mux3-protocol/blob/main/contracts/core/management/FacetManagement.sol): [0xA1418018B06147e1C3aef8D873cd95130684e033](https://arbiscan.io/address/0xA1418018B06147e1C3aef8D873cd95130684e033) | | | | | [FacetReader](https://github.com/mux-world/mux3-protocol/blob/main/contracts/core/reader/FacetReader.sol): [0x831dca42A5f95761F0679c8e388aE1a296C613D1](https://arbiscan.io/address/0x831dca42A5f95761F0679c8e388aE1a296C613D1) | | | | | [FacetOpen](https://github.com/mux-world/mux3-protocol/blob/main/contracts/core/trade/FacetOpen.sol): [0xe1619504Aca3A6944511352CA6fF73ec2dc52460](https://arbiscan.io/address/0xe1619504Aca3A6944511352CA6fF73ec2dc52460) | | | | | [FacetClose](https://github.com/mux-world/mux3-protocol/blob/main/contracts/core/trade/FacetClose.sol): [0xEB678f40e2b3b208e5A89c9d1d3b08aEbe109e47](https://arbiscan.io/address/0xEB678f40e2b3b208e5A89c9d1d3b08aEbe109e47) | | | | | [FacetPositionAccount](https://github.com/mux-world/mux3-protocol/blob/main/contracts/core/trade/FacetPositionAccount.sol): [0x7B0F526779E75490d7c7aD179A284B8C34CD997B](https://arbiscan.io/address/0x7B0F526779E75490d7c7aD179A284B8C34CD997B) | | [OrderBook](https://github.com/mux-world/mux3-protocol/blob/main/contracts/orderbook/OrderBook.sol) | yes | [0x8ec387586a709ECE1a9Ea83c6163c3616D8E16b4](https://arbiscan.io/address/0x8ec387586a709ECE1a9Ea83c6163c3616D8E16b4) | [0x0f4DfD1CEAbb84C2e79645B71dA321D09203ea39](https://arbiscan.io/address/0x0f4DfD1CEAbb84C2e79645B71dA321D09203ea39) | | [Delegator](https://github.com/mux-world/mux3-protocol/blob/main/contracts/orderbook/Delegator.sol) | yes | [0xEf501d58e8d09eE8D8f28Cf812D5F57384e5d7B0](https://arbiscan.io/address/0xEf501d58e8d09eE8D8f28Cf812D5F57384e5d7B0) | [0xbe002aFa6281f1fdE05B6E67280D14F986aE5597](https://arbiscan.io/address/0xbe002aFa6281f1fdE05B6E67280D14F986aE5597) | | [Mux3FeeDistributor](https://github.com/mux-world/mux3-protocol/blob/main/contracts/peripherals/Mux3FeeDistributor.sol) | yes | [0x8824b3464dAb29Fc68cC8c74D5eAd8B05054E5F8](https://arbiscan.io/address/0x8824b3464dAb29Fc68cC8c74D5eAd8B05054E5F8) | [0xb9943B7DA8933C199a7D3aE4dFf62316eb480b6f](https://arbiscan.io/address/0xb9943B7DA8933C199a7D3aE4dFf62316eb480b6f) | | [CollateralPool](https://github.com/mux-world/mux3-protocol/blob/main/contracts/pool/CollateralPool.sol) | yes | | [0x91cf3E76b198fff00E77B9812d1D0f67459Ee189](https://arbiscan.io/address/0x91cf3E76b198fff00E77B9812d1D0f67459Ee189) | | [CollateralPoolEventEmitter](https://github.com/mux-world/mux3-protocol/blob/main/contracts/pool/CollateralPoolEventEmitter.sol) | yes | [0xFf5Bb66f074EfEc32daCA30f562e55e19F1eD758](https://arbiscan.io/address/0xFf5Bb66f074EfEc32daCA30f562e55e19F1eD758) | [0xe9944E142cc0312dd93C3729767B30Ac9cF8c9cB](https://arbiscan.io/address/0xe9944E142cc0312dd93C3729767B30Ac9cF8c9cB) | | [Mux3POL](https://github.com/mux-world/mux3-protocol/blob/main/contracts/peripherals/Mux3POL.sol) | yes | [0x3d1BF07B62EfCd553b0fDE81d0A4354444320F9a](https://arbiscan.io/address/0x3d1BF07B62EfCd553b0fDE81d0A4354444320F9a) | [0x2ef6D4B46C71f7eA0b8D0309F342100d3a5Cf7A6](https://arbiscan.io/address/0x2ef6D4B46C71f7eA0b8D0309F342100d3a5Cf7A6) | | [CollateralPoolAumReader](https://github.com/mux-world/mux3-protocol/blob/main/contracts/peripherals/CollateralPoolAumReader.sol) | yes | [0x661dFB22fa624A09De093b82177A19b323f46A09](https://arbiscan.io/address/0x661dFB22fa624A09De093b82177A19b323f46A09) | [0x445C1Cea6f052F8e413894812474a3A50e0a01de](https://arbiscan.io/address/0x445C1Cea6f052F8e413894812474a3A50e0a01de) | | [CallbackRegister](https://github.com/mux-world/mux3-protocol/blob/main/contracts/peripherals/CallbackRegister.sol) | yes | [0xd2Df81619E20C6699B7f2153f8A2395e5Bb2C74C](https://arbiscan.io/address/0xd2Df81619E20C6699B7f2153f8A2395e5Bb2C74C) | [0x482DD8D90Cfbe5DC4cB8ea8865A654512a4d7A51](https://arbiscan.io/address/0x482DD8D90Cfbe5DC4cB8ea8865A654512a4d7A51) | | [ChainlinkStreamProvider](https://github.com/mux-world/mux3-protocol/blob/main/contracts/orderbook/providers/ChainlinkStreamProvider.sol) | yes | [0x381200de35Cd57810F5AB9a6273eaD68917961e2](https://arbiscan.io/address/0x381200de35Cd57810F5AB9a6273eaD68917961e2) | [0x61D7cf411922913a6A0DED4A2374bF469BDB2D97](https://arbiscan.io/address/0x61D7cf411922913a6A0DED4A2374bF469BDB2D97) | | [MuxPriceProvider](https://github.com/mux-world/mux3-protocol/blob/main/contracts/orderbook/providers/MuxPriceProvider.sol) | yes | [0x18b930154300607538895dbE21359C8ae224695A](https://arbiscan.io/address/0x18b930154300607538895dbE21359C8ae224695A) | [0x6a82D843d8e753BCf60EDaeAE7B2b66856950138](https://arbiscan.io/address/0x6a82D843d8e753BCf60EDaeAE7B2b66856950138) | | [Swapper](https://github.com/mux-world/mux3-protocol/blob/main/contracts/peripherals/Swapper.sol) | yes | [0x0D37BC91a3F1807cf4305E4A5eDEb4Ee47FA7112](https://arbiscan.io/address/0x0D37BC91a3F1807cf4305E4A5eDEb4Ee47FA7112) | [0xd18E07Ec76e04228422d6650aC5c334f1fe608Be](https://arbiscan.io/address/0xd18E07Ec76e04228422d6650aC5c334f1fe608Be) | # MUX Leveraged Trading Protocol Contracts ## Arbitrum | Contract Name | Upgradeable | Proxy Address | Implementation Address | | ---------------------------------------------------------------------------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [LiquidityPool](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPool.sol) | yes | [0x3e0199792Ce69DC29A0a36146bFa68bd7C8D6633](https://arbiscan.io/address/0x3e0199792Ce69DC29A0a36146bFa68bd7C8D6633) | [Hop1](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPoolHop1.sol): [0x9588535Df27aEAD7BBf2520892852B220ec36F15](https://arbiscan.io/address/0x9588535Df27aEAD7BBf2520892852B220ec36F15) | | | | | [Hop2](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPoolHop2.sol): [0xad367F665AeEb1D57764BbDcBFAB5Be5327632dA](https://arbiscan.io/address/0xad367F665AeEb1D57764BbDcBFAB5Be5327632dA) | | [OrderBook](https://github.com/mux-world/mux-protocol/blob/main/contracts/orderbook/OrderBook.sol) | yes | [0xa19fD5aB6C8DCffa2A295F78a5Bb4aC543AAF5e3](https://arbiscan.io/address/0xa19fD5aB6C8DCffa2A295F78a5Bb4aC543AAF5e3) | [0xFD92e0b7107488b095cA98E50BE128fee2a35879](https://arbiscan.io/address/0xFD92e0b7107488b095cA98E50BE128fee2a35879) | | [LiquidityManager](https://github.com/mux-world/mux-protocol/blob/main/contracts/liquidity/LiquidityManager.sol) | yes | [0x02FAe054ACD7FB1615471319c4E3029DFbC2B23C](https://arbiscan.io/address/0x02FAe054ACD7FB1615471319c4E3029DFbC2B23C) | [0xcd5daf9cF3CCa8Ff41Effd74D9437C432b31C358](https://arbiscan.io/address/0xcd5daf9cF3CCa8Ff41Effd74D9437C432b31C358) | | [MuxTimelock](https://github.com/mux-world/mux-protocol/blob/main/contracts/governance/MuxTimelock.sol) | yes | [0xc2D28778447B1B0B2Ae3aD17dC6616b546FBBeBb](https://arbiscan.io/address/0xc2D28778447B1B0B2Ae3aD17dC6616b546FBBeBb) | [0x965A4597258F0cbb57B513846e0D89109300D7C5](https://arbiscan.io/address/0x965A4597258F0cbb57B513846e0D89109300D7C5) | | [NativeUnwrapper](https://github.com/mux-world/mux-protocol/blob/main/contracts/components/NativeUnwrapper.sol) | no | [0x675807f847A5802539B5895F9c12E55b7864b213](https://arbiscan.io/address/0x675807f847A5802539B5895F9c12E55b7864b213) | | | [Vault](https://github.com/mux-world/mux-protocol/blob/main/contracts/governance/Vault.sol) | yes | [0x917952280770Daa800E1B4912Ea08450Bf71d57e](https://arbiscan.io/address/0x917952280770Daa800E1B4912Ea08450Bf71d57e) | [0x33261B56d71d8AF545aFcf255779149788CeeD62](https://arbiscan.io/address/0x33261B56d71d8AF545aFcf255779149788CeeD62) | | [POL](https://github.com/mux-world/mux-protocol/blob/main/contracts/governance/POL.sol) | yes | [0x18891480b9dd2aC5eF03220C45713d780b5CFdeF](https://arbiscan.io/address/0x18891480b9dd2aC5eF03220C45713d780b5CFdeF) | [0x338097e546106ca0cD53ED2C7dA1bfcdF4eE9c3e](https://arbiscan.io/address/0x338097e546106ca0cD53ED2C7dA1bfcdF4eE9c3e) | | [Reader](https://github.com/mux-world/mux-protocol/blob/main/contracts/reader/Reader.sol) | no | [0xF64B4bD682E792e0BA78956B86F2Cee946d2E7D6](https://arbiscan.io/address/0xF64B4bD682E792e0BA78956B86F2Cee946d2E7D6) | | | [MUXLP](https://github.com/mux-world/mux-protocol/blob/main/contracts/tokens/MlpToken.sol) | yes | [0x7CbaF5a14D953fF896E5B3312031515c858737C8](https://arbiscan.io/address/0x7CbaF5a14D953fF896E5B3312031515c858737C8) | [0x085F5B8945426Aa5e8239CD172070d0301Fe33BA](https://arbiscan.io/address/0x085F5B8945426Aa5e8239CD172070d0301Fe33BA) | | [MuxUSD](https://github.com/mux-world/mux-protocol/blob/main/contracts/tokens/MuxToken.sol) | yes | [0x458cd4Bd5ae8FCF602a910423C30323997E497c3](https://arbiscan.io/address/0x458cd4Bd5ae8FCF602a910423C30323997E497c3) | [0xcCD84810375992d7E19d1529150B1B29eA2EfF6B](https://arbiscan.io/address/0xcCD84810375992d7E19d1529150B1B29eA2EfF6B) | | [MuxETH](https://github.com/mux-world/mux-protocol/blob/main/contracts/tokens/MuxToken.sol) | yes | [0xE03b9Bf45B8b717237380AB934C5A6a5CA4C2Af1](https://arbiscan.io/address/0xE03b9Bf45B8b717237380AB934C5A6a5CA4C2Af1) | [0xcCD84810375992d7E19d1529150B1B29eA2EfF6B](https://arbiscan.io/address/0xcCD84810375992d7E19d1529150B1B29eA2EfF6B) | | [MuxBTC](https://github.com/mux-world/mux-protocol/blob/main/contracts/tokens/MuxToken.sol) | yes | [0x2aC61dd4fBb11919b20A3859D4dDc4Fa192c8ba1](https://arbiscan.io/address/0x2aC61dd4fBb11919b20A3859D4dDc4Fa192c8ba1) | [0xcCD84810375992d7E19d1529150B1B29eA2EfF6B](https://arbiscan.io/address/0xcCD84810375992d7E19d1529150B1B29eA2EfF6B) | | [MuxAVAX](https://github.com/mux-world/mux-protocol/blob/main/contracts/tokens/MuxToken.sol) | yes | [0xd8d05915cf0AccBBBa78720707920Aff6eef3943](https://arbiscan.io/address/0xd8d05915cf0AccBBBa78720707920Aff6eef3943) | [0xcCD84810375992d7E19d1529150B1B29eA2EfF6B](https://arbiscan.io/address/0xcCD84810375992d7E19d1529150B1B29eA2EfF6B) | | [MuxBNB](https://github.com/mux-world/mux-protocol/blob/main/contracts/tokens/MuxToken.sol) | yes | [0xdd3CF6B0182993eced98fD71962dfA18E2eae2E4](https://arbiscan.io/address/0xdd3CF6B0182993eced98fD71962dfA18E2eae2E4) | [0xcCD84810375992d7E19d1529150B1B29eA2EfF6B](https://arbiscan.io/address/0xcCD84810375992d7E19d1529150B1B29eA2EfF6B) | | [MuxFTM](https://github.com/mux-world/mux-protocol/blob/main/contracts/tokens/MuxToken.sol) | yes | [0x198F152D3F34cb49A926333cD935D864D398753F](https://arbiscan.io/address/0x198F152D3F34cb49A926333cD935D864D398753F) | [0xcCD84810375992d7E19d1529150B1B29eA2EfF6B](https://arbiscan.io/address/0xcCD84810375992d7E19d1529150B1B29eA2EfF6B) | | [MuxOP](https://github.com/mux-world/mux-protocol/blob/main/contracts/tokens/MuxToken.sol) | yes | [0x854CF75e51782dE84478B1518543920f35a13eaE](https://arbiscan.io/address/0x854CF75e51782dE84478B1518543920f35a13eaE) | [0xcCD84810375992d7E19d1529150B1B29eA2EfF6B](https://arbiscan.io/address/0xcCD84810375992d7E19d1529150B1B29eA2EfF6B) | | [MUX](https://github.com/mux-world/mux-staking/blob/main/contracts/token/Mux.sol) | yes | [0x8BB2Ac0DCF1E86550534cEE5E9C8DED4269b679B](https://arbiscan.io/address/0x8BB2Ac0DCF1E86550534cEE5E9C8DED4269b679B) | [0x454C4eA9e1593805c7d40f34E6e3C8C39ec20d8A](https://arbiscan.io/address/0x454C4eA9e1593805c7d40f34E6e3C8C39ec20d8A) | | [MlpFeeRewardTracker](https://github.com/mux-world/mux-staking/blob/main/contracts/rewardTracker/MlpRewardTracker.sol) | yes | [0x290450cDea757c68E4Fe6032ff3886D204292914](https://arbiscan.io/address/0x290450cDea757c68E4Fe6032ff3886D204292914) | [0xB0cF86a9E40Df2DAFC05f9750bd18c51d3D69330](https://arbiscan.io/address/0xB0cF86a9E40Df2DAFC05f9750bd18c51d3D69330) | | [MlpMuxRewardTracker](https://github.com/mux-world/mux-staking/blob/main/contracts/rewardTracker/MlpRewardTracker.sol) | yes | [0x0a9bbf8299FEd2441009a7Bb44874EE453de8e5D](https://arbiscan.io/address/0x0a9bbf8299FEd2441009a7Bb44874EE453de8e5D) | [0xB0cF86a9E40Df2DAFC05f9750bd18c51d3D69330](https://arbiscan.io/address/0xB0cF86a9E40Df2DAFC05f9750bd18c51d3D69330) | | [MlpVester](https://github.com/mux-world/mux-staking/blob/main/contracts/Vester.sol) | yes | [0xBCF8c124975DE6277D8397A3Cad26E2333620226](https://arbiscan.io/address/0xBCF8c124975DE6277D8397A3Cad26E2333620226) | [0xeb8c86df0d57c653a58e71d6c7237ed4187adc40](https://arbiscan.io/address/0xeb8c86df0d57c653a58e71d6c7237ed4187adc40) | | [RewardRouter](https://github.com/mux-world/mux-staking/blob/main/contracts/RewardRouter.sol) | yes | [0xaf9C4F6A0ceB02d4217Ff73f3C95BbC8c7320ceE](https://arbiscan.io/address/0xaf9C4F6A0ceB02d4217Ff73f3C95BbC8c7320ceE) | [0x7fbd0c4d87bf25eb355aeaf23856e3d6791184dd](https://arbiscan.io/address/0x7fbd0c4d87bf25eb355aeaf23856e3d6791184dd) | | [VotingEscrow](https://github.com/mux-world/mux-staking/blob/main/contracts/VotingEscrow.sol) | yes | [0xA65bA125a25b51539a3d10910557b28215097810](https://arbiscan.io/address/0xA65bA125a25b51539a3d10910557b28215097810) | [0x5172205CA5b352BC429EE2904D0297b7aCB3F785](https://arbiscan.io/address/0x5172205CA5b352BC429EE2904D0297b7aCB3F785) | | [VeFeeRewardTracker](https://github.com/mux-world/mux-staking/blob/main/contracts/rewardTracker/MuxRewardTracker.sol) | yes | [0x9357e3b52fd40CA943264D7c85550D97530ae94E](https://arbiscan.io/address/0x9357e3b52fd40CA943264D7c85550D97530ae94E) | [0x28345899567fa8eF459b5BB171d63E0719affd16](https://arbiscan.io/address/0x28345899567fa8eF459b5BB171d63E0719affd16) | | [VeMuxRewardTracker](https://github.com/mux-world/mux-staking/blob/main/contracts/rewardTracker/MuxRewardTracker.sol) | yes | [0x2245c73C01Bad2404be0B13B852534C9672bE696](https://arbiscan.io/address/0x2245c73C01Bad2404be0B13B852534C9672bE696) | [0x28345899567fa8eF459b5BB171d63E0719affd16](https://arbiscan.io/address/0x28345899567fa8eF459b5BB171d63E0719affd16) | | [MuxVester](https://github.com/mux-world/mux-staking/blob/main/contracts/Vester.sol) | yes | [0xD7e864658DdE98B1A1d70ce6d84D78e0A8e8aD18](https://arbiscan.io/address/0xD7e864658DdE98B1A1d70ce6d84D78e0A8e8aD18) | [0xeb8c86df0d57c653a58e71d6c7237ed4187adc40](https://arbiscan.io/address/0xeb8c86df0d57c653a58e71d6c7237ed4187adc40) | | [FeeDistributor](https://github.com/mux-world/mux-staking/blob/main/contracts/distributor/FeeDistributor.sol) | yes | [0x6256dc556EE340952b8d8778f22608fd45592859](https://arbiscan.io/address/0x6256dc556EE340952b8d8778f22608fd45592859) | [0xC30992d3ab2289d7510D18f25D6cF7e9275C4ec1](https://arbiscan.io/address/0xC30992d3ab2289d7510D18f25D6cF7e9275C4ec1) | | [MuxDistributor](https://github.com/mux-world/mux-staking/blob/main/contracts/distributor/MuxDistributor.sol) | yes | [0xF66937704923DE6FF7cD51861F772C1eB1C431e9](https://arbiscan.io/address/0xF66937704923DE6FF7cD51861F772C1eB1C431e9) | [0xC8efD5D238cCF8b4d1C859Bf4dCe1dc3bf1AD667](https://arbiscan.io/address/0xC8efD5D238cCF8b4d1C859Bf4dCe1dc3bf1AD667) | | [ReferralManager](https://github.com/mux-world/mux-protocol/blob/main/contracts/referral/ReferralManager.sol) | yes | [0xa68d96F26112377abdF3d6b9fcde9D54f2604C2a](https://arbiscan.io/address/0xa68d96F26112377abdF3d6b9fcde9D54f2604C2a) | [0xb90FE34008CCECE311dF043E64D4e330741f6d21](https://arbiscan.io/address/0xb90FE34008CCECE311dF043E64D4e330741f6d21) | | [Disperse](https://github.com/mux-world/mux-protocol/blob/main/contracts/referral/Disperse.sol) | yes | [0x39A6567C3E01d28c37403c8782DE78490D9204fA](https://arbiscan.io/address/0x39A6567C3E01d28c37403c8782DE78490D9204fA) | [0x9e9f9B289B711209Db5A5dFEDeB1b06B5f5d978A](https://arbiscan.io/address/0x9e9f9B289B711209Db5A5dFEDeB1b06B5f5d978A) | ## Avalanche | Contract Name | Upgradeable | Proxy Address | Implementation Address | | ---------------------------------------------------------------------------------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [LiquidityPool](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPool.sol) | yes | [0x0bA2e492e8427fAd51692EE8958eBf936bEE1d84](https://snowtrace.io/address/0x0bA2e492e8427fAd51692EE8958eBf936bEE1d84) | [Hop1](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPoolHop1.sol): [0x18968A52c97AA26BEc6cEDdC77D314641433C82a](https://snowtrace.io/address/0x18968A52c97AA26BEc6cEDdC77D314641433C82a) | | | | | [Hop2](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPoolHop2.sol): [0xd4b442Dcca6d807cf9e038faab66Ed2C9F10c935](https://snowtrace.io/address/0xd4b442Dcca6d807cf9e038faab66Ed2C9F10c935) | | [OrderBook](https://github.com/mux-world/mux-protocol/blob/main/contracts/orderbook/OrderBook.sol) | yes | [0x5898c3E218a8501533d771C86e2fA37743ea2aDd](https://snowtrace.io/address/0x5898c3E218a8501533d771C86e2fA37743ea2aDd) | [0x1ea32f93cd1EdFbdd8279f7cFC1Da9546E0e5B3B](https://snowtrace.io/address/0x1ea32f93cd1EdFbdd8279f7cFC1Da9546E0e5B3B) | | [LiquidityManager](https://github.com/mux-world/mux-protocol/blob/main/contracts/liquidity/LiquidityManager.sol) | yes | [0x28f16eB86481066Bf63BcBEB05C8474f7120A36C](https://snowtrace.io/address/0x28f16eB86481066Bf63BcBEB05C8474f7120A36C) | [0x9D4A8d7523a36f4a2E99870f1aFf232ded7e95Ae](https://snowtrace.io/address/0x9D4A8d7523a36f4a2E99870f1aFf232ded7e95Ae) | | [MuxTimelock](https://github.com/mux-world/mux-protocol/blob/main/contracts/governance/MuxTimelock.sol) | yes | [0xe013756fE041c524F0583e644fFC00Ed13bdc938](https://snowtrace.io/address/0xe013756fE041c524F0583e644fFC00Ed13bdc938) | [0x973db3142aa601ef11c1C8148e6EA8e7A4eE6B07](https://snowtrace.io/address/0x973db3142aa601ef11c1C8148e6EA8e7A4eE6B07) | | [NativeUnwrapper](https://github.com/mux-world/mux-protocol/blob/main/contracts/components/NativeUnwrapper.sol) | no | [0x350C9CCEb837e45119e97fb4b95F3B0A28F79C79](https://snowtrace.io/address/0x350C9CCEb837e45119e97fb4b95F3B0A28F79C79) | | | [Vault](https://github.com/mux-world/mux-protocol/blob/main/contracts/governance/Vault.sol) | yes | [0x29a28cC3FdC128693ef6a596eF45c43ff63B7062](https://snowtrace.io/address/0x29a28cC3FdC128693ef6a596eF45c43ff63B7062) | [0x7a1AE37F17269dD604EA291E87A3064Ac97f27C5](https://snowtrace.io/address/0x7a1AE37F17269dD604EA291E87A3064Ac97f27C5) | | [Reader](https://github.com/mux-world/mux-protocol/blob/main/contracts/reader/Reader.sol) | no | [0xCE443B8c1C3E3edb3b9F3B2B482FaaC09A95B01d](https://snowtrace.io/address/0xCE443B8c1C3E3edb3b9F3B2B482FaaC09A95B01d) | | | MUXLP | no | [0xAf2D365e668bAaFEdcFd256c0FBbe519e594E390](https://snowtrace.io/address/0xAf2D365e668bAaFEdcFd256c0FBbe519e594E390) | | | MuxUSD | no | [0xEA4B1b0aa3C110c55f650d28159Ce4AD43a4a58b](https://snowtrace.io/address/0xEA4B1b0aa3C110c55f650d28159Ce4AD43a4a58b) | | | MuxETH | no | [0xDE53842F87c95362B2912DB5dBBA404E7D5Ff842](https://snowtrace.io/address/0xDE53842F87c95362B2912DB5dBBA404E7D5Ff842) | | | MuxBTC | no | [0xCd7D33c265c811ee12c956D28c0e91f32a65119d](https://snowtrace.io/address/0xCd7D33c265c811ee12c956D28c0e91f32a65119d) | | | MuxAVAX | no | [0xaC80096d53c5965D9432592D28687C521472b9EB](https://snowtrace.io/address/0xaC80096d53c5965D9432592D28687C521472b9EB) | | | MuxBNB | no | [0x30a667dF8562a2460F45AC297D833a36FEaC0C2F](https://snowtrace.io/address/0x30a667dF8562a2460F45AC297D833a36FEaC0C2F) | | | MuxFTM | no | [0x70D30270ccC356f47E5782a1A905ea85B9E08CEa](https://snowtrace.io/address/0x70D30270ccC356f47E5782a1A905ea85B9E08CEa) | | | MuxOP | no | [0xE80e0B928F8f3024dfeFa56E7608bC3bAF389881](https://snowtrace.io/address/0xE80e0B928F8f3024dfeFa56E7608bC3bAF389881) | | | [ReferralManager](https://github.com/mux-world/mux-protocol/blob/main/contracts/referral/ReferralManager.sol) | yes | [0x1444edF22cd6C891391f3644b435eF6b8270C4B0](https://snowtrace.io/address/0x1444edF22cd6C891391f3644b435eF6b8270C4B0) | [0x127963cD8253bb54c19E266e5EcC6bad8d30a96E](https://snowtrace.io/address/0x127963cD8253bb54c19E266e5EcC6bad8d30a96E) | ## BNB Chain | Contract Name | Upgradeable | Proxy Address | Implementation Address | | ---------------------------------------------------------------------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [LiquidityPool](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPool.sol) | yes | [0x855E99F768FaD76DD0d3EB7c446C0b759C96D520](https://bscscan.com/address/0x855E99F768FaD76DD0d3EB7c446C0b759C96D520) | [Hop1](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPoolHop1.sol): [0x1C9Bf593c077c346D375CB8D7110BD5295E95Dd1](https://bscscan.com/address/0x1C9Bf593c077c346D375CB8D7110BD5295E95Dd1) | | | | | [Hop2](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPoolHop2.sol): [0x3e3AE3250A51851242f59d2876dB3147A3A9706F](https://bscscan.com/address/0x3e3AE3250A51851242f59d2876dB3147A3A9706F) | | [OrderBook](https://github.com/mux-world/mux-protocol/blob/main/contracts/orderbook/OrderBook.sol) | yes | [0xa67aA293642C4e02D1b9F360b007C0dBDc451A08](https://bscscan.com/address/0xa67aA293642C4e02D1b9F360b007C0dBDc451A08) | [0x914997af2d4062e8fc2877FAF4f7C66B6101BDDD](https://bscscan.com/address/0x914997af2d4062e8fc2877FAF4f7C66B6101BDDD) | | [LiquidityManager](https://github.com/mux-world/mux-protocol/blob/main/contracts/liquidity/LiquidityManager.sol) | yes | [0xee85CDdCe0CF068091081eA0fcd53f279aa3B09F](https://bscscan.com/address/0xee85CDdCe0CF068091081eA0fcd53f279aa3B09F) | [0x2dE35ab97d23aEFd2B0E38A17787298f41819391](https://bscscan.com/address/0x2dE35ab97d23aEFd2B0E38A17787298f41819391) | | [MuxTimelock](https://github.com/mux-world/mux-protocol/blob/main/contracts/governance/MuxTimelock.sol) | yes | [0x4B94654aa3351a3ede1173b9B3E3414431eCA2d3](https://bscscan.com/address/0x4B94654aa3351a3ede1173b9B3E3414431eCA2d3) | [0x4aBC472F340001245E0C2854F6f691179931EB59](https://bscscan.com/address/0x4aBC472F340001245E0C2854F6f691179931EB59) | | [NativeUnwrapper](https://github.com/mux-world/mux-protocol/blob/main/contracts/components/NativeUnwrapper.sol) | no | [0x2b9d445Dc03fECd49d52DA986b5AcA38A7E7771d](https://bscscan.com/address/0x2b9d445Dc03fECd49d52DA986b5AcA38A7E7771d) | | | [Vault](https://github.com/mux-world/mux-protocol/blob/main/contracts/governance/Vault.sol) | yes | [0x8D751570BA1Fd8a8ae89E4B27d18bf6C321Aab0a](https://bscscan.com/address/0x8D751570BA1Fd8a8ae89E4B27d18bf6C321Aab0a) | [0x6d9c3405eb89816e56733A1944F2D1Ce1E2C702d](https://bscscan.com/address/0x6d9c3405eb89816e56733A1944F2D1Ce1E2C702d) | | [Reader](https://github.com/mux-world/mux-protocol/blob/main/contracts/reader/Reader.sol) | no | [0x9897A73a606606394FA2324D16f3926f5963a9C3](https://bscscan.com/address/0x9897A73a606606394FA2324D16f3926f5963a9C3) | | | MUXLP | no | [0x07145Ad7C7351c6FE86b6B841fC9Bed74eb475A7](https://bscscan.com/address/0x07145Ad7C7351c6FE86b6B841fC9Bed74eb475A7) | | | MuxUSD | no | [0x523d3e0DacD7c470Ebe8880AbE808161696CeBeC](https://bscscan.com/address/0x523d3e0DacD7c470Ebe8880AbE808161696CeBeC) | | | MuxETH | no | [0xEA09cBb3f286F7c1a377C4Db825c1cefaD2476AE](https://bscscan.com/address/0xEA09cBb3f286F7c1a377C4Db825c1cefaD2476AE) | | | MuxBTC | no | [0x904d0221641232fb40f99dc92C1d59c35698Ff0B](https://bscscan.com/address/0x904d0221641232fb40f99dc92C1d59c35698Ff0B) | | | MuxAVAX | no | [0x81421A49c2Bb3F2F77A666F0686B4dB47A26360C](https://bscscan.com/address/0x81421A49c2Bb3F2F77A666F0686B4dB47A26360C) | | | MuxBNB | no | [0x0Acc63843f9dd5C2A14EE7C2349859c526B9d4D3](https://bscscan.com/address/0x0Acc63843f9dd5C2A14EE7C2349859c526B9d4D3) | | | MuxFTM | no | [0xF234437596B9C90231181a2E80c668C4e5408108](https://bscscan.com/address/0xF234437596B9C90231181a2E80c668C4e5408108) | | | MuxOP | no | [0x8FEB4121c45265515f36925ca412F85588c00b7E](https://bscscan.com/address/0x8FEB4121c45265515f36925ca412F85588c00b7E) | | | [ReferralManager](https://github.com/mux-world/mux-protocol/blob/main/contracts/referral/ReferralManager.sol) | yes | [0x3EfE4639eb082e22209fee29aAbaf14Ade5bF82B](https://bscscan.com/address/0x3EfE4639eb082e22209fee29aAbaf14Ade5bF82B) | [0xB66755BeE3967b015BBA2232048C9D43D0b52782](https://bscscan.com/address/0xB66755BeE3967b015BBA2232048C9D43D0b52782) | ## Fantom | Contract Name | Upgradeable | Proxy Address | Implementation Address | | ---------------------------------------------------------------------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [LiquidityPool](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPool.sol) | yes | [0x2e81F443A11a943196c88afcB5A0D807721A88E6](https://ftmscan.com/address/0x2e81F443A11a943196c88afcB5A0D807721A88E6) | [Hop1](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPoolHop1.sol): [0x480894501D4050763d3b54e741bb82fD5F91dF89](https://ftmscan.com/address/0x480894501D4050763d3b54e741bb82fD5F91dF89) | | | | | [Hop2](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPoolHop2.sol): [0xE6F4e843E15Ca0a96DB77FAA31EC5e5E297Cd8C3](https://ftmscan.com/address/0xE6F4e843E15Ca0a96DB77FAA31EC5e5E297Cd8C3) | | [OrderBook](https://github.com/mux-world/mux-protocol/blob/main/contracts/orderbook/OrderBook.sol) | yes | [0x0c30b10462CdED51C3CA31e7C51019b7d25a965B](https://ftmscan.com/address/0x0c30b10462CdED51C3CA31e7C51019b7d25a965B) | [0x450D81f80D0f29Ba8F12Ea6d291Cc3A52cBF9718](https://ftmscan.com/address/0x450D81f80D0f29Ba8F12Ea6d291Cc3A52cBF9718) | | [LiquidityManager](https://github.com/mux-world/mux-protocol/blob/main/contracts/liquidity/LiquidityManager.sol) | yes | [0x5898c3E218a8501533d771C86e2fA37743ea2aDd](https://ftmscan.com/address/0x5898c3E218a8501533d771C86e2fA37743ea2aDd) | [0x9eA320d5b987e859D841e7624E5e845928bA2ADc](https://ftmscan.com/address/0x9eA320d5b987e859D841e7624E5e845928bA2ADc) | | [MuxTimelock](https://github.com/mux-world/mux-protocol/blob/main/contracts/governance/MuxTimelock.sol) | yes | [0xb5e423dc5014aD8bC1a1DAFE8Eb9DfA1994F594D](https://ftmscan.com/address/0xb5e423dc5014aD8bC1a1DAFE8Eb9DfA1994F594D) | [0xE780D906F25D4A49133231C2C3332c5C1A1ae9c7](https://ftmscan.com/address/0xE780D906F25D4A49133231C2C3332c5C1A1ae9c7) | | [NativeUnwrapper](https://github.com/mux-world/mux-protocol/blob/main/contracts/components/NativeUnwrapper.sol) | no | [0xc9296e12e2Fe55605d9F6dB5412EaA1938F0B404](https://ftmscan.com/address/0xc9296e12e2Fe55605d9F6dB5412EaA1938F0B404) | | | [Vault](https://github.com/mux-world/mux-protocol/blob/main/contracts/governance/Vault.sol) | yes | [0xdAF2064F52F123EE1D410e97C2df549c23a99683](https://ftmscan.com/address/0xdAF2064F52F123EE1D410e97C2df549c23a99683) | [0xe6006167d82B59bcA33e3CE2688F79eddA5cF8fF](https://ftmscan.com/address/0xe6006167d82B59bcA33e3CE2688F79eddA5cF8fF) | | [Reader](https://github.com/mux-world/mux-protocol/blob/main/contracts/reader/Reader.sol) | no | [0x30acc119F8b60C9cb92b8E3c4c7f8830c82f707E](https://ftmscan.com/address/0x30acc119F8b60C9cb92b8E3c4c7f8830c82f707E) | | | MUXLP | no | [0xDDAde9a8dA4851960DFcff1AE4A18EE75C39eDD2](https://ftmscan.com/address/0xDDAde9a8dA4851960DFcff1AE4A18EE75C39eDD2) | | | MuxUSD | no | [0xC70107ae20A976C958bF39B32eF8A6E0D2f04878](https://ftmscan.com/address/0xC70107ae20A976C958bF39B32eF8A6E0D2f04878) | | | MuxETH | no | [0x13cCB790Cc6e3735b6b0eC11fef1A81703892861](https://ftmscan.com/address/0x13cCB790Cc6e3735b6b0eC11fef1A81703892861) | | | MuxBTC | no | [0x1305b25842778041c4ae0c9e7C264A617c619FD4](https://ftmscan.com/address/0x1305b25842778041c4ae0c9e7C264A617c619FD4) | | | MuxAVAX | no | [0x746Ba48fC973596d0077573BDa6185cA3BB9c3dC](https://ftmscan.com/address/0x746Ba48fC973596d0077573BDa6185cA3BB9c3dC) | | | MuxBNB | no | [0x0b70Ad251761fCFf7Cb42dB35b10Ea0208ECd07c](https://ftmscan.com/address/0x0b70Ad251761fCFf7Cb42dB35b10Ea0208ECd07c) | | | MuxFTM | no | [0xFCCa7fA56e26f0C86339Ec06D304151aa2E9647A](https://ftmscan.com/address/0xFCCa7fA56e26f0C86339Ec06D304151aa2E9647A) | | | MuxOP | no | [0xF16f662BC827C7e2D28F4B5F4f47cA9Cad63E424](https://ftmscan.com/address/0xF16f662BC827C7e2D28F4B5F4f47cA9Cad63E424) | | | [ReferralManager](https://github.com/mux-world/mux-protocol/blob/main/contracts/referral/ReferralManager.sol) | yes | [0x3EfE4639eb082e22209fee29aAbaf14Ade5bF82B](https://ftmscan.com/address/0x3EfE4639eb082e22209fee29aAbaf14Ade5bF82B) | [0x9D4A8d7523a36f4a2E99870f1aFf232ded7e95Ae](https://ftmscan.com/address/0x9D4A8d7523a36f4a2E99870f1aFf232ded7e95Ae) | ## Optimism | Contract Name | Upgradeable | Proxy Address | Implementation Address | | ---------------------------------------------------------------------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [LiquidityPool](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPool.sol) | yes | [0xc6BD76FA1E9e789345e003B361e4A0037DFb7260](https://optimistic.etherscan.io/address/0xc6BD76FA1E9e789345e003B361e4A0037DFb7260) | [Hop1](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPoolHop1.sol): [0x0532e5f80688308d11Aafa2ffb003C0dFfB4Fbc3](https://optimistic.etherscan.io/address/0x0532e5f80688308d11Aafa2ffb003C0dFfB4Fbc3) | | | | | [Hop2](https://github.com/mux-world/mux-protocol/blob/main/contracts/core/LiquidityPoolHop2.sol): [0x7ae9fDE6121d6433153654e7f80c0E003591045C](https://optimistic.etherscan.io/address/0x7ae9fDE6121d6433153654e7f80c0E003591045C) | | [OrderBook](https://github.com/mux-world/mux-protocol/blob/main/contracts/orderbook/OrderBook.sol) | yes | [0x6Fde9892Fd5302ac3c68688085BD5b031A63BC9D](https://optimistic.etherscan.io/address/0x6Fde9892Fd5302ac3c68688085BD5b031A63BC9D) | [0xd19Cc219177A42b93621153D7F050C3467d5C34D](https://optimistic.etherscan.io/address/0xd19Cc219177A42b93621153D7F050C3467d5C34D) | | [LiquidityManager](https://github.com/mux-world/mux-protocol/blob/main/contracts/liquidity/LiquidityManager.sol) | yes | [0xFEc3704f4A02cB0EE6C7d52Cbf72b11E0441E9d5](https://optimistic.etherscan.io/address/0xFEc3704f4A02cB0EE6C7d52Cbf72b11E0441E9d5) | [0x7E647AF347dA9122684E39A456562ccf6B09b391](https://optimistic.etherscan.io/address/0x7E647AF347dA9122684E39A456562ccf6B09b391) | | [MuxTimelock](https://github.com/mux-world/mux-protocol/blob/main/contracts/governance/MuxTimelock.sol) | yes | [0x9A383F154EE344d51381727395A6C9004c6494B6](https://optimistic.etherscan.io/address/0x9A383F154EE344d51381727395A6C9004c6494B6) | [0xb3568690BfA5ED29dA99ec2F395FF1859cc90b9E](https://optimistic.etherscan.io/address/0xb3568690BfA5ED29dA99ec2F395FF1859cc90b9E) | | [NativeUnwrapper](https://github.com/mux-world/mux-protocol/blob/main/contracts/components/NativeUnwrapper.sol) | no | [0xee4B6c9Db5d5AA948bdE5E3223B0277849C45f48](https://optimistic.etherscan.io/address/0xee4B6c9Db5d5AA948bdE5E3223B0277849C45f48) | | | [Vault](https://github.com/mux-world/mux-protocol/blob/main/contracts/governance/Vault.sol) | yes | [0x39d653884B611E0A8dbdb9720Ad5D75642fd544b](https://optimistic.etherscan.io/address/0x39d653884B611E0A8dbdb9720Ad5D75642fd544b) | [0x68e13c91Fc1b8dca877D88d5d48E7B4bc9d6afC3](https://optimistic.etherscan.io/address/0x68e13c91Fc1b8dca877D88d5d48E7B4bc9d6afC3) | | [Reader](https://github.com/mux-world/mux-protocol/blob/main/contracts/reader/Reader.sol) | no | [0xdF88Fe94EF674D8c1ab1743AD88717E7AE893a44](https://optimistic.etherscan.io/address/0xdF88Fe94EF674D8c1ab1743AD88717E7AE893a44) | | | MUXLP | no | [0x0509474f102b5cd3f1f09e1E91feb25938eF0f17](https://optimistic.etherscan.io/address/0x0509474f102b5cd3f1f09e1E91feb25938eF0f17) | | | MuxUSD | no | [0xE80e0B928F8f3024dfeFa56E7608bC3bAF389881](https://optimistic.etherscan.io/address/0xE80e0B928F8f3024dfeFa56E7608bC3bAF389881) | | | MuxETH | no | [0xff86404162BF14Fe50CEdcF82A56941DC5F48c77](https://optimistic.etherscan.io/address/0xff86404162BF14Fe50CEdcF82A56941DC5F48c77) | | | MuxBTC | no | [0x1bba8683E28078306db88743a387EB34Fb5f34Ed](https://optimistic.etherscan.io/address/0x1bba8683E28078306db88743a387EB34Fb5f34Ed) | | | MuxAVAX | no | [0x50Ec9b92b3bD46969B1AE5E10543Ca6fB49Fba4f](https://optimistic.etherscan.io/address/0x50Ec9b92b3bD46969B1AE5E10543Ca6fB49Fba4f) | | | MuxBNB | no | [0x253BE9F0e2A8749dF6aC7466D096B264788745e0](https://optimistic.etherscan.io/address/0x253BE9F0e2A8749dF6aC7466D096B264788745e0) | | | MuxFTM | no | [0xfd951e71A8Ec5C03AD6139d35F800374Ba500fA8](https://optimistic.etherscan.io/address/0xfd951e71A8Ec5C03AD6139d35F800374Ba500fA8) | | | MuxOP | no | [0x69663Eb604C7d534e9149fa855D89d9104E75363](https://optimistic.etherscan.io/address/0x69663Eb604C7d534e9149fa855D89d9104E75363) | | | [ReferralManager](https://github.com/mux-world/mux-protocol/blob/main/contracts/referral/ReferralManager.sol) | yes | [0xc9296e12e2Fe55605d9F6dB5412EaA1938F0B404](https://optimistic.etherscan.io/address/0xc9296e12e2Fe55605d9F6dB5412EaA1938F0B404) | [0x497C0d498EFe06D99E7Cd3334c7A2865e63C5c7c](https://optimistic.etherscan.io/address/0x497C0d498EFe06D99E7Cd3334c7A2865e63C5c7c) | # MUX Aggregator Contracts ## Arbitrum | Contract Name | Upgradeable | Proxy Address | Implementation Address | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | [ProxyFactory](https://github.com/mux-world/mux-aggregator-protocol/blob/main/contracts/proxyFactory/ProxyFactory.sol) | yes | [0x2ff2f1D9826ae2410979ae19B88c361073Ab0918](https://arbiscan.io/address/0x2ff2f1D9826ae2410979ae19B88c361073Ab0918) | [0xE0634794dCfD43A158918208DFc7BD1c0D619bCb](https://arbiscan.io/address/0xE0634794dCfD43A158918208DFc7BD1c0D619bCb) | | [GmxAdapter](https://github.com/mux-world/mux-aggregator-protocol/blob/main/contracts/aggregators/gmx/GmxAdapter.sol) | no | [0xe739c5eBd761Bd7398c7F769a7caf29F6AC60f6b](https://arbiscan.io/address/0xe739c5eBd761Bd7398c7F769a7caf29F6AC60f6b) | | | [GmxV2Adapter](https://github.com/mux-world/references/blob/main/\[https:/github.com/mux-world/mux-aggregator-protocol/blob/main/contracts/aggregators/gmx/GmxAdapter.sol]\(https:/github.com/mux-world/mux-aggregator-protocol/blob/main/contracts/aggregators/gmxV2/GmxV2Adapter.sol\)) | no | [0xe1B50BBa2255Bbc60E4d4CDb4c77df61d1fDdd8d](https://arbiscan.io/address/0xe1B50BBa2255Bbc60E4d4CDb4c77df61d1fDdd8d) | | | [Reader](https://github.com/mux-world/mux-aggregator-protocol/blob/main/contracts/reader/Reader.sol) | no | [0x697af744dCe3229cd43a16554B67267686FaDdAc](https://arbiscan.io/address/0x697af744dCe3229cd43a16554B67267686FaDdAc) | | # MUX Degen Contracts ## Arbitrum | Contract Name | Upgradeable | Proxy Address | Implementation Address | | ------------------------------------------------------------------------------------------------------------------------------ | ----------- | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [DegenPool](https://github.com/mux-world/mux-degen-protocol/blob/main/contracts/third-party/Diamond.sol) | yes | [0x2f977A859eD91c729c781ba0e50927d5Da3Cb988](https://arbiscan.io/address/0x2f977A859eD91c729c781ba0e50927d5Da3Cb988) | [Trade](https://github.com/mux-world/mux-degen-protocol/blob/main/contracts/facets/Trade.sol): [0x8cEE7ee9B7A1e56933C206855a9249011B9d12BE](https://arbiscan.io/address/0x8cEE7ee9B7A1e56933C206855a9249011B9d12BE) | | | | | [Liquidity](https://github.com/mux-world/mux-degen-protocol/blob/main/contracts/facets/Liquidity.sol): [0x24bd1bf44Ff06CE1Ef547A9ba286754822f2f752](https://arbiscan.io/address/0x24bd1bf44Ff06CE1Ef547A9ba286754822f2f752) | | | | | [Getter](https://github.com/mux-world/mux-degen-protocol/blob/main/contracts/facets/Getter.sol): [0xdC3BA816d6cbf7800B072FbDe29965aF66224d13](https://arbiscan.io/address/0xdC3BA816d6cbf7800B072FbDe29965aF66224d13) | | | | | [Admin](https://github.com/mux-world/mux-degen-protocol/blob/main/contracts/facets/Admin.sol): [0x3B9d9E7af6df90af51b1182820d6FCf3CD3dDA71](https://arbiscan.io/address/0x3B9d9E7af6df90af51b1182820d6FCf3CD3dDA71) | | | | | [Account](https://github.com/mux-world/mux-degen-protocol/blob/main/contracts/facets/Account.sol): [0x9047C47cc569F6eaC82f3459f69da1DeCf78D4BB](https://arbiscan.io/address/0x9047C47cc569F6eaC82f3459f69da1DeCf78D4BB) | | [OrderBook](https://github.com/mux-world/mux-degen-protocol/blob/main/contracts/orderbook/OrderBook.sol) | yes | [0xab7bD145CC9B68b1904D4B6Ca93056f503C5aA19](https://arbiscan.io/address/0xab7bD145CC9B68b1904D4B6Ca93056f503C5aA19) | [0xF01D26A7fBc5d32CF3a37A5b17491C858D216720](https://arbiscan.io/address/0xF01D26A7fBc5d32CF3a37A5b17491C858D216720) | | [DLP](https://github.com/mux-world/mux-degen-protocol/blob/main/contracts/peripherals/MlpToken.sol) | yes | [0xb1BCa2B964cbD0450ae47Cd7c40431Bc5B237D18](https://arbiscan.io/address/0xb1BCa2B964cbD0450ae47Cd7c40431Bc5B237D18) | [0x8AcB0Ca30e865Bf8f063E803D859bEc7aFdF8A7A](https://arbiscan.io/address/0x8AcB0Ca30e865Bf8f063E803D859bEc7aFdF8A7A) | | [DegenPOL](https://github.com/mux-world/mux-degen-protocol/blob/main/contracts/peripherals/DegenPOL.sol) | yes | [0x5571E4227510A8FF52723A7dd15BE5CF331DDAca](https://arbiscan.io/address/0x5571E4227510A8FF52723A7dd15BE5CF331DDAca) | [0xEB13A62Df5425F10707097D612d22BD1C6fb07ec](https://arbiscan.io/address/0xEB13A62Df5425F10707097D612d22BD1C6fb07ec) | | [Reader](https://github.com/mux-world/mux-degen-protocol/blob/main/contracts/reader/Reader.sol) | no | [0x25aB6cA91979714a2DC06512618F6eCC66e3B7fD](https://arbiscan.io/address/0xF64B4bD682E792e0BA78956B86F2Cee946d2E7D6) | | | [DegenFeeDistributor](https://github.com/mux-world/mux-degen-protocol/blob/main/contracts/peripherals/DegenFeeDistributor.sol) | yes | [0xE1d14373120312205cB2974823F8a76E7Eeaf2ec](https://arbiscan.io/address/0xE1d14373120312205cB2974823F8a76E7Eeaf2ec) | [0x77Ea372DD760b9F25F9E6D31999D8cBABb351EA0](https://arbiscan.io/address/0x77Ea372DD760b9F25F9E6D31999D8cBABb351EA0) | # MUXLP Tranches Contracts | Contract Name | Upgradeable | Proxy Address | Implementation Address | | -------------------------------------------------------------------------------------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | [TranchePOL](https://github.com/mux-world/muxlp-tranches-protocol/blob/main/contracts/peripherals/TranchePOL.sol) | yes | [0xbFBda4D31db778798527fB45Fc82F1b65017466d](https://arbiscan.io/address/0xbFBda4D31db778798527fB45Fc82F1b65017466d) | [0x48Fa7d65f2a5751982d0999457C0a2EB9F88Ff6D](https://arbiscan.io/address/0x48Fa7d65f2a5751982d0999457C0a2EB9F88Ff6D) | | [SeniorVault](https://github.com/mux-world/muxlp-tranches-protocol/blob/main/contracts/senior/SeniorVault.sol) | yes | [0x99615f5480B716690e6Fb2875bcf4a87a61CE198](https://arbiscan.io/address/0x99615f5480B716690e6Fb2875bcf4a87a61CE198) | [0xcc6deA720eA14290b0f0a022DA5c16eB238cD141](https://arbiscan.io/address/0xcc6deA720eA14290b0f0a022DA5c16eB238cD141) | | [JuniorVault](https://github.com/mux-world/muxlp-tranches-protocol/blob/main/contracts/junior/JuniorVault.sol) | yes | [0x883774d2c63a3D7a461a27aF620aB23B8796b50e](https://arbiscan.io/address/0x883774d2c63a3D7a461a27aF620aB23B8796b50e) | [0xac96E14B8897ABa253Efe2299B0724E5009395fD](https://arbiscan.io/address/0xac96E14B8897ABa253Efe2299B0724E5009395fD) | | [RouterV1](https://github.com/mux-world/muxlp-tranches-protocol/blob/main/contracts/router/RouterV1.sol) | yes | [0x9B637AeE65106B1d55CEA5d560Fd0C67Ce1F18C5](https://arbiscan.io/address/0x9B637AeE65106B1d55CEA5d560Fd0C67Ce1F18C5) | [0x645a63752B27949BAe50947244D1c072Dc02F9d3](https://arbiscan.io/address/0x645a63752B27949BAe50947244D1c072Dc02F9d3) | | [RewardController](https://github.com/mux-world/muxlp-tranches-protocol/blob/main/contracts/reward/RewardController.sol) | yes | [0xb68Ac7D3E3833DeB35fc5D63c16E3B5da12a9A41](https://arbiscan.io/address/0xb68Ac7D3E3833DeB35fc5D63c16E3B5da12a9A41) | [0xC90A587502eCaa3464DcD72f31B2420cA750B2FC](https://arbiscan.io/address/0xC90A587502eCaa3464DcD72f31B2420cA750B2FC) | | [SeniorRewardDistributor](https://github.com/mux-world/muxlp-tranches-protocol/blob/main/contracts/reward/RewardDistributor.sol) | yes | [0x809e14CE17E03eFe7cdbD7eb674B2dC18619f41C](https://arbiscan.io/address/0x809e14CE17E03eFe7cdbD7eb674B2dC18619f41C) | [0x594839f47e7F12ff36846430E1900a6633d86e40](https://arbiscan.io/address/0x594839f47e7F12ff36846430E1900a6633d86e40) | | [JuniorRewardDistributor](https://github.com/mux-world/muxlp-tranches-protocol/blob/main/contracts/reward/RewardDistributor.sol) | yes | [0x623CCA95790bF7C07FAd104ed1c4334DB30a5299](https://arbiscan.io/address/0x623CCA95790bF7C07FAd104ed1c4334DB30a5299) | [0x594839f47e7F12ff36846430E1900a6633d86e40](https://arbiscan.io/address/0x594839f47e7F12ff36846430E1900a6633d86e40) | | [SeniorConfig](https://github.com/mux-world/muxlp-tranches-protocol/blob/main/contracts/senior/SeniorConfig.sol) | no | [0xbE08Ad8DAf5b919eD76E8a51Ad1ebA853a3Deb9D](https://arbiscan.io/address/0xbE08Ad8DAf5b919eD76E8a51Ad1ebA853a3Deb9D) | | | [JuniorConfig](https://github.com/mux-world/muxlp-tranches-protocol/blob/main/contracts/junior/JuniorConfig.sol) | no | [0x5DfCDE5060B67640A0FE2E42380b67D3f8EAb3fF](https://arbiscan.io/address/0x5DfCDE5060B67640A0FE2E42380b67D3f8EAb3fF) | | | [RouterConfig](https://github.com/mux-world/muxlp-tranches-protocol/blob/main/contracts/router/RouterConfig.sol) | no | [0xf0d95EDAbB0CfA923B5d52BF4504Ac64df451C69](https://arbiscan.io/address/0xf0d95EDAbB0CfA923B5d52BF4504Ac64df451C69) | | # MUX API The API returns the MUXLP price and the liquidity distribution. ## Endpoint Get all assets liquidity info of MUX protocol. ``` https://app.mux.network/api/liquidityAsset ``` ## Response | Field | Description | | ------------------ | ------------------------------------------------------------ | | status | 0 for success. -1 for internal error. -2 for invalid request | | totalValue | Total pool value in dollars | | stableUtilization | %utilization of stable coins | | muxLPPrice | MUXLP price in dollars | | muxLPTotalBalance | MUXLP token balance in all chains | | isLPPriceAvailable | true if add/remove liquidity is enabled | | assets | Listed assets on MUX | | distribution | Distribution of assets on each chain | Structure of "assets": | Field | Description | | ----------------- | ------------------------------------------------------------------------- | | symbol | Asset symbol like "ETH", "BTC", ... | | isStable | Is a stable coin | | price | Asset price | | value | Asset total value on all chains in US dollars | | lpBalance | Asset amount in MUXLP pool | | credit | Asset credit amount for MUX Aggregator | | longs | Long position size | | shorts | Short position size | | targetWeight | Target weight of asset | | actualWeight | Actual weight of asset in MUXLP pool | | utility | Margin trading utilization | | availableForLong | Available long position size | | availableForShort | Available short position size | | liquidityOnChains | Asset value on each chain and asset amount can be removed from each chain | Structure of "distribution": | Field | Description | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | muxMarginTrading | margin trading value (long positions and short positions) on all chains in US dollars | | dexs | Third party DEXes list on MUX, in which "value" means total value in the DEX in US dollars, "targetWeight" means target weight of this DEX, "actualWeight" means actual weight of this DEX | # Bug Bounty [MUX Bug Bounty Program](https://immunefi.com/bounty/mux/) # Terms * [Terms & Conditions](https://mux.network/#/terms-and-conditions) * [Referral Terms](https://mux.network/#/referral-terms) # Trade On MUX, traders can open up to 100x leveraged positions with zero price impact. In addition, the protocol offers multiple collateral options, limit & trigger orders, [dark oracle](https://github.com/mux-world/references/blob/main/MECHANISMS.md#dark-oracle) pricing, and other trader-friendly features for an optimized on-chain trading experience. There are currently five markets on the platform: ETH, BTC, AVAX, BNB and FTM; more markets to come in the future. [Product Page: Trade](https://app.mux.network/#/trade?chainId=42161\&market=ETH\&collateral=ETH) ## Connect Wallet ![](/files/z9hHEwi9jSQ9IVoZkv7N) Step 1: Click the “Connect Wallet” button to open the Connect Wallet dialog. ![](/files/fyFPddz9r7ngO1hpDHgy) Step 2: Select the type of wallet you would like to use. If you haven’t installed a browser wallet, it is recommended to install [MetaMask](https://metamask.io/). ## Select Network ![](/files/HAoLWtsnzphvrm8oL8Dd) Step 1: MUX is deployed on Arbitrum, Avalanche, BNB Chain and Fantom; you can select the network you prefer to use from the menu. ![](/files/N0EFG0Fbsur8E9T3WwAW) Step 2: After choosing a network, you need to confirm this action in your wallet. If the selected network hasn’t been added to your wallet, MUX will ask for approval to add the network. ![](/files/qsmgAwqmefLuulKvsa7s) Note：The "Wrong Network" state will appear if the network you use in the wallet doesn't match the selected network on MUX. By clicking the "Wrong Network" button or the "Please Use ... Wallet" button, the wallet window will pop up for switching the network to match the one used on MUX. ## Select Market ![](/files/9XgHPM1FXt5g2sm4H6Bq) Click the market button on the info bar or trading panel to open the dialog, then select the market / underlying asset you would like to trade. ## Open Position ![](/files/f1nCSvThNe5v5K2zWvQu) Step 1: Select the side for your position. For long positions, you will make profits when the underlying asset price rises and have losses when the price drops; for short positions, you will make profits when the underlying asset price drops and have losses when the price rises. ![](/files/q05JV19k5gvMRM9oZUgd) Step 2: Select the order type you need to use. Three order types are available: Market Order, Limit Order and Trigger Order. **Market Order** Fill orders with the latest market price. **Limit Order** Buy / Long: Fill orders when the mark price is lower than or equal to the limit price. Sell / Short: Fill orders when the mark price is higher than or equal to the limit price. **Trigger Order** Buy / Long: Fill orders when the mark price is higher than or equal to the trigger price. Sell / Short: Fill orders when the mark price is lower than or equal to the trigger price. ![](/files/wa2NPx7GywwJ3SbnJ06s) Step 3: Select your preferred collateral option. ![](/files/kRDQfts7D8atnJdarMdX) Step 4: Enter the amount of collateral or underlying asset for the position; the fields will adjust for each other accordingly. Then, adjust the position leverage using the input field, slider or shortcuts. Using leverage will increase your exposure to market fluctuations, and the liquidation risks will increase accordingly. Please be mindful of risk management. Users can use up to 100x leverage on MUX. The product also allows leverage under 1x and input with up to one decimal. ![](/files/iijcF5ZK33t4Cfd0gVHt) **Available Liquidity** The available liquidity is the current position size cap. The example above indicates the traders can long up to 1.8376 ETH at the moment. The available liquidity is calculated separately for long and short positions; it will change along with the total open interest. **Profits In** If this position is closed, your realized profits will be settled in the indicated asset, and there are three scenarios. * The realized profits will be settled in the underlying assets for long positions. * For short positions, the realized profits will be settled in stablecoins. Users can choose the preferred type of stablecoin to receive upon position closure. * For long positions with underlying assets that don’t exist on the current chain (for example, longing AVAX on Arbitrum,) the realized profits will be settled in stablecoins. Under the circumstance when the current chain has insufficient tokens reserved, some of the profits might be settled in [muxTokens](/tutorials/redeem). Users can redeem muxTokens into related tokens on a network with sufficient reserves. **Liquidation Price** Once the mark price reaches the liquidation price, the position will be liquidated. Liquidation happens when the collateral value has fallen below the maintenance margin, which is the minimum amount of collateral required to keep the position open. **Collateral** The position collateral is the number of tokens used, deducting the fees. **Fees** The open fee will be 0.075% of the position value and deducted from the collateral upon opening. **Spread** The spread is the difference between the ask and bid prices for the asset. The spread is 0% under the ETH and BTC markets on MUX. ![](/files/cyz3QlLSJ2Nl2iyJ33c3) Step 5: Depending on the position type, click the “Long” or “Short” button to open the confirmation dialog, then click the “Confirm” button to open the wallet and submit the order. ![](/files/YjgN7AvZ1wAW8AVRWXfd) Market orders will appear under "Positions" immediately after they are submitted. Limit or Trigger orders will appear under "Open Orders." ## Price, Open Interest, Funding, Chart ![](/files/6Cc9Uq032NzpWxf04tbh) The displayed information are market name, asset index price, price 24H change, long & short open interests under the market and estimated 1H funding rate. The index prices on MUX come from the [dark oracle](https://github.com/mux-world/references/blob/main/MECHANISM.md#dark-oracle), which aggregates price feeds from multiple sources to ensure accuracy and stability. With this mechanism, traders can open positions of any size with zero price impact. The funding rates are calcualted seperatly for long and short postions on MUX, and the payments will be collected every 8 hours. Funding payments will be settled when traders apply changes to positions. ## Change Collateral ![](/files/W9Cq184f3Y2DImexFGbR) Click the “+” button to open the “Change Collateral” dialog, then add or remove collateral based on your needs. Increased collateral lowers the leverage, and decreased collateral raises the leverage. ## Cancel Order ![](/files/XieLBBOoZSrE23rPlWT8) Click the “Cancel” button to open the confirmation dialog, then confirm to cancel the order if needed. ## Trade History ![](/files/o3lh7R0bCpKGsu85zq5s) The trade history will be displayed chronologically, from the latest to the earliest. In addition, you can filter the history by period, market and type. ![](/files/wHVrhq2pdwnMSgpFYNjk) MUX allows users to download trade history into spreadsheets. The filters that you are using will be applied to the spreadsheet. ## Close Position ![](/files/XOU2ITS5alR13lLgkQBa) Click the “Close” button to open the dialog, then enter the amount to close. You will receive the collateral tokens with the PNL applied after closing the position. The profits will be settled in the underlying asset or stablecoins, and the losses will be deducted from the collateral. **Fully Close** When you close the position by 100%, the position size will be reduced to 0, and you will receive all the collateral tokens with the total PNL applied. **Partially Close - Don’t Maintain Leverage** When you close part of the position without maintaining leverage, the position size will reduce by the amount you entered without withdrawing any collateral; only the PNL from the closed amount will be settled. **Partially Close - Maintain Leverage** When you close part of the position and maintain leverage, the position size will reduce by the amount you entered, and a corresponding amount of collateral tokens will be withdrawn with the PNL applied. ![](/files/FTbYdkMxHT2yZZ7FDhtA) Three order types are available for closing a position: Market Order, Limit Order and Stop Loss Order. **Market Order** * Fill orders with the latest market price. **Limit Order** * Long Position: Fill orders when the mark price is higher than or equal to the limit price. * Short Position: Fill orders when the mark price is lower than or equal to the limit price. **Stop Loss Order** * Long Position: Fill orders when the mark price is lower than or equal to the stop price. * Short Position: Fill orders when the mark price is higher than or equal to the stop price. # Provide Liquidity ## Buy MUXLP ![](/files/fHugx1nDT9ojFXFKfOzR) Step 1: Click the “Buy / Sell MUXLP” button on the “Liquidity” page to open the “Buy / Sell MUXLP” page. You can buy or sell MUXLP on any deployed networks: Arbitrum, BNB Chain, Avalanche, Fantom. Please note, although Buy / Sell MUXLP is open on all deployed networks, [MUXLP staking](/tutorials/stake#stake-muxlp) can only take place on Arbitrum. ![](/files/YLZnPdiVYJKbmyFgofRO) Step 2: Click the “Select a Token” button to open the selection dialog; then, choose the token you prefer to use for buying MUXLP. Since the MUXLP pool is a [multi-asset pool](broken://pages/CQ2eNMmJNPnzJseIgrZN#multi-asset-pool), users can provide liquidity with any assets the [portfolio](/protocol/liquidity#muxlp-pool-portfolio) allows. Buying MUXLP is equivalent to purchasing an index of the total pooled assets. Holding MUXLP is not risk-free; please check [LP Profits & Risks](https://github.com/mux-world/references/blob/main/LIQUIDITY.#muxlp-profits-and-risks) for more details. ![](/files/3oyv8zx3aag2K3kBl6qy) Step 3: Enter the number of tokens you would like to use, or the number of MUXLP tokens you would like to receive, then click “Buy MUXLP.” After you click the “Yes Confirm” button and confirm the buy order in your wallet, the payment tokens will be deducted from your wallet, and the broker will use these tokens to fill your buy order. Please note it takes around 15 minutes for the orders to fill. After the order is filled, the MUXLP tokens will be distributed to your wallet directly. ![](/files/jJHXCpW31KMTLQiyA257) Note: After you place a buy order, the processing state will appear; it will disappear after the MUXLP tokens are distributed to your wallet. Please note that only one buy order can be active at a time. Therefore, if you need to place another buy order, you will need to wait until the current order is processed; if you need to change your existing order, you will need to cancel it and place a new one. If needed, you can cancel the order before it’s processed. Your payment tokens will return to your wallet after the order is cancelled. ![](/files/5B8eWrBhIvGfXu3m8gZf) Step 4: After receiving the MUXLP tokens, you can stake them to earn protocol income and MUX rewards. For staking tutorials, please read [MUXLP Staking Tutorials](/tutorials/stake#stake-muxlp). For details regarding income and rewards allocation for MUXLP stakers, please check [Incentives](broken://pages/6ieve53b62fhiLcmovYW). ## Sell MUXLP ![](/files/vaXkZulle8SHwukP801x) Step 1: Click the “Select” button to open the dialog and select the type of token you want to sell your MUXLP into. ![](/files/Uxm21EToWYXTxEhQXqvM) Step 2: Enter the number of MUXLP tokens you would like to sell, or the number of designated tokens you would like to receive, then click “Sell MUXLP.” After you click the “Sell MUXLP” button and confirm the sell order in your wallet, the MUXLP tokens will be deducted from your wallet, and the broker will use these tokens to fill your sell order. Please note it takes around 15 minutes for the orders to fill. After the order is filled, the designated tokens will be distributed to your wallet directly. ![](/files/H90KgnAZoGAnALAKkbvy) Note: After you place a sell order, the processing state will appear; it will disappear after the designated tokens are distributed to your wallet. Please note that only one sell order can be active at a time. Therefore, if you need to place another sell order, you will need to wait until the current order is processed; if you need to change your existing order, you will need to cancel it and place a new one. If needed, you can cancel the order before it’s processed. Your MUXLP tokens will return to your wallet after the order is cancelled. # Stake ## Stake MUXLP ![](/files/rKVZrZcu924Hgq3JwJla) Before staking MUXLP, please make sure you have purchased MUXLP tokens. ![](/files/9Mblx0gLjCqfzuvhAwH5) Since all staking-related actions take place on Arbitrum, if you have MUXLP tokens on BNB Chain, Avalanche or Fantom, you will need to bridge them to Arbitrum. The MUX protocol has collaborated with Celer Network for a smooth bridging experience; you can bridge your MUXLP tokens via [cBridge](https://cbridge.celer.network/#/transfer). ![](/files/nQF0gKlvmtkVynalyRgf) After your MUXLP tokens are available on Arbitrum, you can start to stake them to earn multiplexed protocol income and MUX rewards. Step 1: Click “Stake MUXLP” to open the “Stake / Unstake MUXLP” dialog. Step 2: Enter the number of MUXLP tokens you want to stake. Step 3: After you finish the input, click “Stake MUXLP” to open the wallet. After confirming the action in your wallet, your MUXLP will be staked. ## Unstake MUXLP ![](/files/RuxuuBHFTUdCqcNHW8Ju) Step 1: Open the “Stake / Unstake MUXLP” dialog and select the “Unstake” tab. Step 2: Enter the number of MUXLP tokens you want to unstake. Step 3: After you finish the input, click “Unstake MUXLP” to open the wallet. After confirming the action in your wallet, your MUXLP will be unstaked. ## veMUX Locked-Staking ![](/files/ZAsrbpLP4zfDghnD5DFz) Step 1: Select to lock MCB or MUX. The locked-staking is only available on Arbitrum; if you have MCB tokens on other networks, please bridge them to Arbitrum before locking. You can bridge MCB tokens via Arbitrum Official Bridge, cBridge or Multichain. ![](/files/MCLRmZASesTMZR7FU1XA) Step 2: Enter the number of MCB or MUX you want lock Step 3: Select your perferred lock time from the date selection window. The minimum lock time is 2 weeks, and the maximum is 4 years. Since the locking is time-weighted, longer locks will be allocated with more veMUX. You can select the lock time by using either the calender or the shortcut buttons. Each week is one epoch for locked-staking, and the epochs start on Thursdays (UTC+0). For non-Thursday locking start dates, the dates will be rounded up to Thursdays. ![](/files/HlVJa4t3gQBUBFd0Snx5) Step 4: After you have finished the input and selected the lock time, click the “Lock MCB/MUX” button to open the confirmation dialog. Step 5: Confirm the locking information on the dialog. If you accept the rules and are ready to lock, check the checkbox and click the “Confirm Locking MCB/MUX” button to show the wallet, then confirm the action on your wallet. Please be aware that once your MCB or MUX tokens are locked, they can’t be unlocked in advance. ## Extend Lock ![](/files/Ti3AaOE9b2jInCNGmZwG) Step 1: Click the “Extend Lock” button to open the dialog. ![](/files/ALoTeQyIT5UuvxV66CgD) Step 2: Click the input field to open the date selection window, then select your preferred date. Step 3: Confirm the locking information on the dialog. If you accept the rules and are ready to extend the lock, check the checkbox and click the “Extend Lock” button to show the wallet, then confirm the action on your wallet. ## Vest MUX ![](/files/bxddZrngV7wNCefOefuB) Step 1: Click the “Vest” button on the channel that you prefer to use to open the vesting dialog ![](/files/rbfFjAGeTPgzcMfv5iQq) Step 2: Enter the number of MUX tokens you want to vest into MCB Step 3: Click the “Vest MUX” button to open the wallet, then confirm the action on your wallet. If you are vesting MUX for the first time, you will need to approve the action first. Once the vesting process starts, the MUX tokens will be converted into MCB over 1 year. ## Terminate Vesting ![](/files/XK1IHScyu9anF0p8q5CM) If you want to withdraw your unvested MUX tokens, you will need to terminate the current vesting process. You can click the “Confirm Withdraw” button to end the vesting process and withdraw all unvested MUX tokens; MUX tokens converted to MCB will remain as MCB. After the vesting process ends, the reserved MUXLP tokens will be unreserved. ## Claim Rewards You can claim rewards from veMUX, staked MUXLP and vested MUX individually, or claim total rewards from the “Overview” page. Please note that since the protocol calculates veMUX rewards weekly, you will receive rewards from veMUX one week after your initial lock starts. # Redeem ![](/files/zRUcU2oHeTai2dnSRvFy) Under the circumstance when the reserved tokens are insufficient on a network, some of taders’ profits might be settled in muxTokens. There are 6 types of muxTokens: muxETH, muxBTC, muxBNB, muxAVAX, muxFTM and muxUSD. After receiving muxTokens, related cards will appear on the “Redeem” page. Users can redeem muxTokens into related tokens on a different network that has sufficient reserves, or wait for the reserves on current network to refill and then redeem. ![](/files/sjBt1njdlD9IKviQw23m) Step 1: Click the “Redeem muxToken” button to open the redemption dialog. Except for muxUSD, all muxTokens only match with one type of token, like muxETH and ETH, muxBTC and BTC; muxUSD can be redeemed into users’ preferred stablecoin. ![](/files/nYcfeXFhl3JYgizz62Gz) Step 2: Select the type of token you want to redeem your muxTokens into. This step only applies to muxUSD redemption. ![](/files/wN1pRoa1FBYDumbRtszm) Step 3: Select the network you want to redeem the muxTokens on. Step 4: Click the “Redeem” button to show your wallet, then confirm the action. If you redeem a type of muxToken for the first time, you need to approve the action. # Referral ![](/files/R9p76eJNLDDiFOpT98Pf) Please use the "As Referrer" tab to create referral codes and earn rebates from your referees' trading fees. Please use the “As Trader” tab to apply a referral code to your account and have a trading fee discount. ## As Referrer - Create Referral Code ![](/files/tefCpY043dc8qMDLshm6) Step 1: Click the “Create Code” button to open the code creation pop-up window. ![](/files/btxUercX12QIQCHgzg2d) Step 2: Enter your preferred code and click “Create” when finished. You will need to confirm this action in your wallet. A referral code can have up to 20 characters; the format allows letters, numbers and underdcore \_ ## As Referrer - Share Referral URL ![](/files/86vbqHOZX1xiRwgUPxaW) After creating the code, click the “Referral URL” button to open the pop-up window and copy the code. You can share the referral URL on your preferred social channels. After users click your referral URL and land on the MUX protocol, your referral code will be automatically applied to their accounts (if they haven’t used a referral code yet.) You will earn rebates from your referees’ trading fees, and the rebates will airdrop to your recipient address weekly. [Learn More](/protocol/referral-program) ![](/files/ULfMd6zPCKPGPLLTFth0) You can tweet your referral URL using the “Tweet” button. ## As Referrer - Code Details Page ![](/files/v29E77ZkrLSiH5YjHawQ) If you need to view the detailed data of a code, click the row of the code to enter the “Code Details” page. ## As Trader - Apply a New Referral Code ![](/files/oNWti2civgUn9nnNZFCA) Step 1: Click “Enter New Code” to open the “Edit Referral Code” pop-up window. Note: If you have clicked on a referral URL previously, then that referral would have been applied to your account. ![](/files/WnpWpUX4LFuQ1LwZDid6) Step 2: Enter the referral code and click “Apply New Code.” After the code is applied, you will start to have trading fee discounts. The discounted fees will be airdropped to your address weekly on Thursday UTC. ## As Trader - Change Applied Referral Code ![](/files/lVkQ8VciraLCrHU1bLwE) If you need to change the referral code, you can click the “Edit Code” button and then apply a new one. ## Code Details - Share Referral URL ![](/files/DoNgo6byGXbFf6UjyZnN) Click the “Referral URL” button to open the pop-up window and copy the code. You can share the referral URL on your preferred social channels. After users click your referral URL and land on the MUX protocol, your referral code will be automatically applied to their accounts (if they haven’t used a referral code yet.) You will earn rebates from your referees’ trading fees, and the rebates will airdrop to your recipient address weekly. [Learn More](/protocol/referral-program) ![](/files/zrPWESiMEBdRJHIjj2S4) You can tweet your Referral URL using the “Tweet” button. ## Code Details - Change Code Recipient Address ![](/files/bBnzQjbbiGQiGEG5fZkn) The rebates earned from the code will airdrop to the recipient's address. By default, the recipient address of your code is your address; however, you can change the rebate recipient address to a different one if needed. Step 1: Click the “Edit Code” button to open the “Change Recipient Address” pop-up window. ![](/files/rHs0MXZz6QFV2lU4mjLs) Step 2: Enter the new recipient address and click the “Change Recipient Address” button. You will need to confirm this action in your wallet. ## Code Details - Transfer Referral Code Ownership ![](/files/XQkd4jQrgMSTOJ5CtVHU) You can transfer the ownership of your referral code to a different address. After the transfer, the recipient address will change to the new owner’s address. Once confirmed, the transfer can’t be undone, so please ensure you enter the correct address. Step 1: Click the “...” button to open the dropdown menu, then click “Transfer Referral Code Ownership.” ![](/files/G3Yo2rx4aY8t6rf3CV2a) Step 2: Enter the new owner’s address. Step 3: Check the confirmation checkbox, then click the “Transfer Referral Code Ownership” button. You will need to confirm this action in your wallet. # Cookie Policy This cookie policy explains what cookies are and how MUX and its affiliates (hereinafter, "MUX," "we," "us," or "our") uses them. We encourage you to read the policy in full so that you understand what information we collect using cookies and how that information is used. By using our sites, you agree that we can use cookies in accordance with this policy. ## What are cookies? Cookies are text files containing small amounts of information, which are downloaded to your browsing device (such as a computer or smartphone) when you visit a website. Cookies can be recognized by the website that downloaded them — or other websites that use the same cookies. This helps websites know if the browsing device has visited them before. ## What are cookies used for? Cookies do lots of different jobs, like helping us understand how our website is being used, letting you navigate between pages efficiently, remembering your preferences, and generally improving your browsing experience. Cookies can also help ensure marketing you see online is more relevant to you and your interests. ## What types of cookies are used by MUX? The types of cookies used on our site can generally be put into one category: analytics. ## Analytics Cookies These cookies collect information about how people are using our website, for example, which pages are visited the most often, how people are moving from one link to another and if they get error messages from certain pages. These cookies don't gather the information that identifies you. All the information these cookies collect is grouped together with information from other people's use of our site on an anonymous basis. Overall, these cookies provide us with analytical information about how our site is performing and how we can improve it. ## How to manage cookies from this website? You can usually use the browser that you are viewing this website through to enable, disable or delete cookies. To do this, follow the instructions provided by your browser (usually located within the "Help," "Tools," or "Edit" settings). Please note that if you set your browser to disable cookies, you may not be able to access secure areas of the website, and other parts of the website may also not work properly. You can find out more information about how to change your browser cookie settings at [www.allaboutcookies.org](http://www.allaboutcookies.org). Some third parties may use Advertising Cookies to help gather information about your browsing activity so that they can deliver website advertising to you that is relevant to your interests. The advertising industries in the EU have developed schemes to help you opt out of receiving cookies used for these purposes. You can find out more about the EU scheme from [www.youronlinechoices.eu](http://www.youronlinechoices.eu) ## Changes Information about the cookies used by us may be updated from time to time, so please check back on a regular basis for any changes.