Skip to main content
AVOID.NET
← MUX Protocol1 decision on this page

Audit log

Every state-changing event for MUX Protocol: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

  1. #1publishby system:backfill
    2026-10-13 05:34:37Z
    Score: ? → ? (no score change)
    anchoranchored
    chain
    ●mainnet-betaslot 456,328,387
    sig
    3YppaeNKmNkD…tjrB46CXexplorer ↗
    hash
    BJP9hfGtr2DE…onZfmbkjsha256 → base58
    verifying row…full verify ↗
    canonical bytes (7840 B) ▸
    {"actor":"system:backfill","investigation_id":"3e1b8101-f1ba-483c-8c70-859670d3984c","kind":"publish","page_slug":"mux-protocol","published_at":"2026-10-13T05:34:37.643Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"MUX Protocol","sections":[{"content":"MUX Protocol describes itself as a protocol suite comprising the MUX Perpetual Aggregator, MUX V3 Trading Protocol, MUX V1 Trading Protocol and MUX V1 Degen Protocol. Secondary reporting states that MCDEX launched its V4 under the MUX name in August 2022 as a multi-chain leveraged trading protocol with up to 100x leverage on Arbitrum, BNB Chain, Avalanche and Fantom. No primary MUX announcement of the rebrand was located; the date rests on secondary sources (BloFin, CoinMarketCap, Dealroom). The aggregator is described as routing trades across venues such as GMX, gTrade (Gains) and MUX's own pools; sources are not fully consistent on the current integration list.","heading":"Overview and history","severity":"low","sources":[{"credibility":2,"name":"MUX documentation overview","type":"official","url":"https://docs.mux.network/"},{"credibility":3,"name":"BloFin: MCDEX Rebranded as MUX","type":"news_article","url":"https://blofin.com/news/mcdex-rebranded-as-mux-launched-multi-chain-leveraged-trading-protocol"},{"credibility":3,"name":"Dealroom: MCDEX","type":"other","url":"https://app.dealroom.co/companies/mcdex"}]},{"content":"DefiLlama's API for MUX Protocol, read on 2026-10-13, showed per-chain TVL of Arbitrum about $8.89M, Avalanche about $0.45M, BSC about $0.32M, OP Mainnet about $0.21M and Fantom about $1,400, summing to roughly $9.86M, with Arbitrum about 90% of the total. This differs from the roughly $9.0M figure supplied by the requester on 2026-10-07, which is consistent with TVL moving between reads. The Arbitrum concentration means the protocol's liquidity depends heavily on a single chain.","heading":"TVL and chain concentration","severity":"low","sources":[{"credibility":2,"name":"DefiLlama API: mux-protocol","type":"on_chain","url":"https://api.llama.fi/protocol/mux-protocol"}]},{"content":"DefiLlama lists the token as MCB at contract 0x4e352cf164e64adcbad318c3a1e222e9eba4ce42 (CoinGecko ID mcdex, CoinMarketCap ID 5956). A ForkLog community article reports a total MCB supply of about 4.8 million, with 1 million reserved for MUX vesting, and that maximum supply can be changed by governance vote. CoinMarketCap listed a max supply of 4,803,143 MCB and a circulating supply of 3,821,523 at the time of the search snapshot; these figures were not independently verified and may be stale. Locking MCB yields veMUX, which per secondary sources entitles holders to a share of protocol revenue and MUX rewards. A governance-adjustable supply cap is a structural risk factor for holders.","heading":"MCB token and tokenomics","severity":"medium","sources":[{"credibility":2,"name":"DefiLlama API: mux-protocol","type":"on_chain","url":"https://api.llama.fi/protocol/mux-protocol"},{"credibility":3,"name":"ForkLog Community Hub: MUX","type":"news_article","url":"https://forklog.com/hub-archive/mux-multichejn-torgovlya-s-ispolzovaniem-zaemnyh-sredstv/"},{"credibility":3,"name":"CoinMarketCap: MUX Protocol (MCB)","type":"other","url":"https://coinmarketcap.com/currencies/mcdex/"}]},{"content":"MUX documentation lists three audits: Guardian Audits for the MUX V3 Trading Protocol (no date stated), SolidProof for the Leveraged Trading Aggregator (report filename indicates 2022-12-15; the page itself does not state a date), and CertiK for the MUX V1 Trading Protocol (no date stated). Report PDFs were not read for this page, so findings and remediation status are unverified. The Immunefi listing offers a maximum bounty of $100,000 for critical smart contract issues and has been live since June 2021, but showed a status of 'Paused' with a last-updated date of 2026-04-30 when read. The Immunefi page lists no specific audits. The scope of audits relative to currently deployed contracts was not verified.","heading":"Audits and bug bounty","severity":"medium","sources":[{"credibility":2,"name":"MUX docs: Audit","type":"official","url":"https://docs.mux.network/protocol/audit.md"},{"credibility":2,"name":"Immunefi: MUX bug bounty","type":"official","url":"https://immunefi.com/bug-bounty/mux/"},{"credibility":2,"name":"MUX docs: Bug Bounty","type":"official","url":"https://docs.mux.network/protocol/bug-bounty.md"}]},{"content":"Searches for exploit, hack, pause or vulnerability reports specific to MUX Protocol returned no results. This is an absence of evidence from a limited search and not confirmation that no incident has occurred; DefiLlama's hacks dashboard and MUX's own channels were not directly checked. Other Arbitrum perpetuals venues have reportedly suffered exploits, and MUX's aggregator routes to third-party venues, so exposure to integrated venues' risks is possible, though no MUX loss from such events was found.","heading":"Incidents","severity":"low","sources":[{"credibility":2,"name":"Decrypt: AFX Trade drained (context on Arbitrum perps)","type":"news_article","url":"https://decrypt.co/374133/arbitrum-perp-dex-afx-trade-drained-of-24m-offers-hacker-30-to-return-it"}]}],"sources_used":[{"credibility":2,"name":"MUX documentation overview","type":"official","url":"https://docs.mux.network/"},{"credibility":2,"name":"MUX docs: Audit","type":"official","url":"https://docs.mux.network/protocol/audit.md"},{"credibility":2,"name":"MUX docs: Bug Bounty","type":"official","url":"https://docs.mux.network/protocol/bug-bounty.md"},{"credibility":2,"name":"Immunefi: MUX bug bounty","type":"official","url":"https://immunefi.com/bug-bounty/mux/"},{"credibility":2,"name":"DefiLlama API: mux-protocol","type":"on_chain","url":"https://api.llama.fi/protocol/mux-protocol"},{"credibility":3,"name":"BloFin: MCDEX Rebranded as MUX","type":"news_article","url":"https://blofin.com/news/mcdex-rebranded-as-mux-launched-multi-chain-leveraged-trading-protocol"},{"credibility":3,"name":"Dealroom: MCDEX","type":"other","url":"https://app.dealroom.co/companies/mcdex"},{"credibility":3,"name":"ForkLog Community Hub: MUX","type":"news_article","url":"https://forklog.com/hub-archive/mux-multichejn-torgovlya-s-ispolzovaniem-zaemnyh-sredstv/"},{"credibility":3,"name":"CoinMarketCap: MUX Protocol (MCB)","type":"other","url":"https://coinmarketcap.com/currencies/mcdex/"},{"credibility":2,"name":"Decrypt: AFX Trade drained","type":"news_article","url":"https://decrypt.co/374133/arbitrum-perp-dex-afx-trade-drained-of-24m-offers-hacker-30-to-return-it"}],"summary":"MUX Protocol (formerly MCDEX) is a perpetuals trading protocol and aggregator, deployed mainly on Arbitrum, with the MCB token and a veMUX revenue-sharing model. The research found no reports of a MUX-specific exploit, and its documentation lists three third-party audits. The Immunefi bug bounty page showed a 'Paused' status when read, and the audit documentation lacks dates for two of three audits.","timeline":[{"date":"2021-06","event":"Immunefi bug bounty program for MUX/MCDEX reported live","source":"Immunefi","source_url":"https://immunefi.com/bug-bounty/mux/"},{"date":"2022-08","event":"MCDEX reported to have rebranded as MUX with V4 launch on Arbitrum, BNB Chain, Avalanche and Fantom","source":"BloFin (secondary)","source_url":"https://blofin.com/news/mcdex-rebranded-as-mux-launched-multi-chain-leveraged-trading-protocol"},{"date":"2022-12","event":"SolidProof audit of MUX Leveraged Trading Aggregator (date inferred from report filename)","source":"MUX docs","source_url":"https://docs.mux.network/protocol/audit.md"},{"date":"2026-04","event":"Immunefi MUX bounty page last updated; status shown as Paused when read","source":"Immunefi","source_url":"https://immunefi.com/bug-bounty/mux/"}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision d5e96c48-da76-42b0-8275-6c9349db72ee
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.