Summary: Mitosis is best understood not as a simple bridge or generic yield app, but as a programmable-liquidity control plane built around a hub chain, branch-chain vaults, and curator-like strategy rights. Users deposit assets into branch-chain vaults, receive 1:1 hub-asset representations on Mitosis Chain, and can then opt those assets into Vault Liquidity Frameworks (VLFs) that expose yield opportunities through ERC-4626-style vaults. The reusable mechanism insight is that Mitosis turns cross-chain deposited liquidity into a managed warehouse: strategists decide where idle liquidity is allocated, while merkle-verified call permissions constrain how that liquidity can be deployed into downstream DeFi protocols.
What it does:
Runs a Layer-1 hub chain that combines an EVM execution layer with a Cosmos/CometBFT consensus layer via the Engine API
Lets users deposit assets into branch-chain Mitosis Vaults and receive 1:1 hub assets on Mitosis Chain representing those locked deposits
Exposes Vault Liquidity Frameworks (VLFs) as structured liquidity programs where deposited hub assets can be supplied into ERC-4626-compatible vaults for yield opportunities
Uses strategist-controlled allocation logic to move idle liquidity toward branch-chain strategy executors while the Asset Manager tracks allocated versus idle liquidity across chains
Restricts downstream strategy execution through merkle-verified, pre-approved call sets and protocol-specific decoder/sanitizer contracts rather than leaving strategist actions fully unconstrained
Extends governance across hub-chain contracts, branch-chain contracts, and even consensus-layer modules through timelock-and-entrypoint flows
Uses non-transferable gMITO governance rewards so governance power is earned through staking/validator participation instead of bought directly on a liquid token market
Key claims:
The docs introduction frames Mitosis as a hub-and-spoke system with branch chains, branch-chain vaults, hub assets, validator/gov systems on Mitosis Chain, and VLFs for structured liquidity opportunities
The vault docs say user deposits are locked in branch-chain vaults while 1:1 hub assets are minted on Mitosis Chain, making the core primitive a cross-chain asset warehouse rather than a bridge-only token wrapper
The VLF overview and allocation docs show the important operational role is the strategist, who decides where idle liquidity is allocated across branch chains and strategies, while the Asset Manager keeps the canonical liquidity ledger
The strategy-execution docs show deployed calls are meant to be bounded by merkle-proof verification plus decoder/sanitizer contracts, which is the main mechanism keeping strategist-controlled execution from becoming arbitrary wallet-style custody
The governance docs show Mitosis governance can target hub-chain contracts, branch-chain contracts, and consensus-layer modules, which is analytically important because practical authority is not confined to one chain’s application layer
The gMITO docs explicitly say the governance token is non-transferable and earned through network participation, which reduces direct vote-buying markets but also ties practical influence to validator/reward flows and protocol-defined distribution
The public GitHub repositories describe the protocol as programmable liquidity across multiple chains and protocols, supporting the classification that liquidity programmability is the core product, not just campaign UX
Whitepaper: The docs host a litepaper page that points to an official Google Drive folder, but no stable direct PDF was pulled locally in this pass. The strongest primary materials are the official site, developer docs, and public GitHub repositories; see ../whitepapers/mitosis-primary-sources-2026-05-08.md.