Mezo

  • Name: Mezo
  • URL: https://mezo.org/
  • Category: Bitcoin finance appchain / EVM-compatible Bitcoin banking platform / Bitcoin-backed stablecoin and credit infrastructure
  • Tags: bitcoin-ecosystem ethereum-ecosystem
  • Summary: Mezo is a Bitcoin-backed borrowing stack attached to its own EVM-compatible chain. That is the useful cut. The app, MUSD stablecoin, BTC-denominated gas, and node software all live in one package, so the note is really about combined credit-and-chain operations rather than another grand Bitcoin economic layer pitch.
  • What it does:
    • Lets users borrow against Bitcoin collateral and mint MUSD, which the site describes as a Bitcoin-backed stablecoin pegged 1:1 to the U.S. dollar
    • Offers consumer-facing “earn,” “borrow,” and “build” flows intended to make Bitcoin usable for everyday finance without outright selling BTC
    • Runs an EVM-compatible blockchain where transaction fees are paid in BTC and the reference client (mezod) is a heavily modified Evmos/Cosmos SDK stack using CometBFT consensus, according to the developer docs
    • Provides validator, RPC-node, and seed-node paths through the Mezo Validator Kit, with public open-source repos and deployment guidance
    • Ships developer resources around MUSD integration, wallet connectivity, and Bitcoin-focused application development
  • Key claims:
    • The homepage frames Mezo as “Bitcoin’s Economic Layer” and says it wants users to “live off of Bitcoin, without selling it”
    • The developer getting-started guide says Mezo is fully EVM-compatible, uses BTC as gas, and is built around the mezod client as a modified Evmos/Cosmos SDK implementation
    • The node docs make clear that Mezo supports validator, RPC, and seed-node roles and that the node stack is open source
    • The MUSD product page positions MUSD as a stablecoin fully backed by Bitcoin reserves and designed for borrowing and spending against BTC collateral
    • The legal corpus includes a MiCA crypto-asset whitepaper for the MEZO token, which is useful for current token/governance context even though it is not the same thing as a protocol-architecture whitepaper

Internal linkages