Cowrie Research

dolomite-primary-sources-2026-05-09

3 min read

Dolomite primary sources — 2026-05-09

Classification takeaway

Dolomite is best treated as an internalized-liquidity margin and lending protocol rather than as a plain money market. The key mechanism is the split between an immutable core margin engine and a mutable module layer, combined with virtual/internal liquidity, isolated borrow positions, and rights-retaining wrappers that let users keep using certain asset-native behaviors while borrowing against them. That makes Dolomite useful when asking where control sits once a protocol tries to merge trading, lending, and account management inside one balance-sheet environment.

Primary sources reviewed

  1. Official site — https://dolomite.io/

    • Public product framing around borrowing, zap flows, token design, audits, and immutable-vs-module architecture.

  2. Docs root / protocol overview — https://docs.dolomite.io/

    • Best first-party source for the two-layer architecture.
    • Important for the claims around immutable core, mutable modules, internal liquidity, free flash loans, subaccounts, and rights-retaining integrations.

  3. Developer overview — https://docs.dolomite.io/developer-documentation/dolomite-margin-overview

    • Good concise source for classifying Dolomite Margin as the smart-contract base used by the app and for confirming the protocol’s modular-but-immutable framing.

  4. Risk management — https://docs.dolomite.io/risk-management

    • Main source for oracle policy, market-by-market risk configuration, and breadth of supported assets.
    • Useful because it shows how much practical policy sits in oracle choices and collateral treatment.

  5. Isolation Mode query answer — https://docs.dolomite.io/risk-management.md?ask=Explain%20Isolation%20Mode%20in%20Dolomite,%20including%20how%20it%20changes%20what%20positions%20can%20do%20and%20where%20control%20or%20listing%20discretion%20sits.

    • Best concise source for the borrow-position control surface.
    • Confirms one isolation asset per borrow position, multiple isolation levels, special vault transfer handling, and that isolation mode is irreversible once enabled.

  6. Admin privileges — https://docs.dolomite.io/admin-privileges.md

    • Most important governance/control document.
    • Details the delayed multisig, timelock bypasses, immutable RiskLimits, mutable RiskParams, market-addition powers, oracle/interest setter control, and global-operator risk.

  7. Admin privileges query answer — https://docs.dolomite.io/admin-privileges.md?ask=Summarize%20the%20main%20admin%20privileges%20and%20which%20parts%20of%20Dolomite%20are%20immutable%20versus%20mutable.

    • Useful concise summary of immutable core vs mutable module/risk surfaces.

  8. Markets / listing query answer — https://docs.dolomite.io/markets.md?ask=Who%20can%20list%20new%20markets%20today%20and%20what%20role%20could%20a%20DAO%20or%20listing%20committee%20play%20later%3F

    • Important because it makes listing discretion explicit.
    • Confirms the protocol administrator lists markets today, while DAO voting rights and a DAO-appointed listing committee may later receive that power.

  9. Protocol repository README — https://raw.githubusercontent.com/dolomite-exchange/dolomite-margin/master/README.md

    • Valuable for lineage and mechanism context.
    • Shows Dolomite as a modified dYdX-derived margin system with changes for large market counts, recyclable markets, global operators, and other risk/governance surfaces.

  10. GitHub organization — https://github.com/dolomite-exchange

    • Useful as the public code surface for the core and modules split.

Why it stays in the active corpus

  • Strong comparison class for lending systems that try to internalize both trading and collateral management instead of keeping them as separate venues.
  • Useful bridge between dYdX-style margin engines, isolated lending markets, and wrapper-heavy asset-integration systems.
  • Adds an analytically important case where “immutable core” does not eliminate governance power, but relocates it into listing, oracle policy, operator approvals, isolation wrappers, and module-layer permissions.

Graph View