Mountain Protocol

• Name: Mountain Protocol
• URL: https://mountainprotocol.com/
• Category: yield-bearing stablecoin issuer / tokenized-cash operator / wind-down governance and redemption workflow boundary
• Tags: ethereum-ecosystem
• Summary: Mountain Protocol belongs in companies/, not mainly projects/, because the durable dependency was a named Bermuda-regulated issuer that controlled USDM issuance and redemption, reserve and bankruptcy-remote structuring, reward policy, supported-chain and partner packaging, and finally the wind-down choreography that replaced direct reserve-backed redemption with exit liquidity through Uniswap. The useful question is not just what did USDM do? but which entity controlled the issuer window, reserve disclosures, redemption rights, and shutdown path once the product stopped growing?
• What it does:
  • Issued USDM, a permissionless ERC-20 stablecoin whose reserves were described as short-duration U.S. Treasuries and equivalent assets held in bankruptcy-remote structures
  • Operated the Mountain Protocol platform for primary-user purchases and redemptions, with different treatment for primary and secondary users
  • Published reserve, structuring, audit, security, and legal materials that made the company-run operating shell legible beyond a single token page
  • Supported multiple EVM chains and DeFi integrations while documenting counterparties such as custodians, compliance vendors, attestations, audits, and onramp providers
  • Ultimately ran the three-phase USDM wind-down in which minting stopped, rewards fell to zero, and direct redemption gave way to redemption through a Uniswap pool backed by another stablecoin
• Key claims:
  • The docs identify Mountain Protocol Limited as a Bermuda-licensed Digital Asset Business and describe the company as directly issuing USDM and operating the Mountain Protocol platform
  • Official reserves docs say USDM reserves were held with regulated financial institutions in bankruptcy-remote, segregated accounts and invested primarily in short-duration U.S. Treasuries or equivalent instruments
  • Legacy product docs frame USDM as a familiar fiat-backed stablecoin model with primary users redeeming 1:1 and secondary users accessing the asset through markets and DeFi
  • The current wind-down docs state that minting has been disabled and that Phase 3 replaces direct reserve-backed redemption with redemption through a Uniswap pool backed by another stablecoin
  • The public GitHub org, audits repo, and OpenZeppelin-hosted security center show Mountain Protocol maintained a relatively transparent operator surface even though the product is winding down
• Whitepaper: No standalone company whitepaper is the important artifact here. The strongest primary materials remain Mountain Protocol’s official site, llms.txt, legacy structuring and reserve docs, wind-down documentation, and public GitHub / security surfaces; see ../whitepapers/mountain-protocol-primary-sources-2026-04-26.md.
• Sources:
  • https://mountainprotocol.com/
  • https://docs.mountainprotocol.com/
  • https://docs.mountainprotocol.com/llms.txt
  • https://docs.mountainprotocol.com/legacy-docs/product-structuring.md
  • https://docs.mountainprotocol.com/legacy-docs/usdm-reserves.md
  • https://docs.mountainprotocol.com/wind-down-documentation/usdm-wind-down-overview.md
  • https://github.com/mountainprotocol
  • https://security.mountainprotocol.com/

Internal linkages

• Project-layer alias: mountain-protocol.
• Strongest issuer and operating-shell comparisons: circle-usdc, paxos, and openeden.
• Useful when the interesting question is not just what backed the token? but who controlled primary issuance, redemption, reserve publication, and the shutdown path?

Protocol / company boundary

• mountain-protocol is intentionally only an alias now because the prior note had already become an issuer and wind-down analysis rather than a clean product or protocol note.
• The durable control surface sits with Mountain Protocol as a named legal entity: reserve structuring, primary-user admission, direct mint-and-redeem workflow, rewards policy, chain expansion, and final wind-down choreography did not reduce cleanly to one token contract.
• If the corpus later needs a separate asset-layer USDM note, keep this company note for the issuer and shutdown boundary. For now the company cut is the sharper taxonomy.

Control surface

• Practical authority sat in primary-user onboarding, reserve and attestation publication, supported chains and counterparties, reward-setting, redemption availability, and the legal shell promising bankruptcy-remote asset segregation.

• The wind-down made the company boundary even clearer: Mountain Protocol decided when minting stopped, when rewards went to zero, and when users had to exit through a Uniswap-based path rather than through direct reserve-backed redemption.

• Read Mountain Protocol as issuer-and-wind-down operator first. USDM was the surface label; the real choke point was the company-managed redemption and disclosure shell behind it.

• Last reviewed: 2026-08-10 UTC