Summary: Ensuro is best understood as an insurance-capital protocol rather than just a blockchain insurer. Its primary docs center the mechanism around RiskModules that originate and price policies, PremiumsAccounts that warehouse expected-loss cashflows, and junior/senior eToken pools that absorb unexpected losses in a defined order. The reusable insight is that Ensuro turns insurance underwriting into a programmable capital stack: expected losses stay with premiums, first-loss risk can be localized to junior pools, and broader balance-sheet support can be shared through senior pools, with governance and upgrade power concentrated in access-managed proxies, timelocks, and security-council style controls.
What it does:
Lets policy partners inject and resolve insurance policies through dedicated RiskModules
Splits policy economics across pure premiums, junior solvency capital, and senior solvency capital
Gives liquidity providers yield exposure through eTokens that earn continuous interest from cost-of-capital charges
Groups insurance products under PremiumsAccounts that can borrow from eToken pools when realized losses exceed collected premiums
Uses upgradeable smart contracts, explicit role systems, and published deployment/audit docs to govern live instances
Key claims:
The docs introduction says Ensuro is a blockchain protocol that provides capital coverage for insurance risks and targets solvency at a chosen confidence interval
The docs and README both describe the core loss waterfall as pure premiums first, then junior eTokens, then senior eTokens
Ensuro’s architecture makes RiskModules the product-level control surface because they own policy injection, pricing validation, and resolution logic
The README and docs show that access control is not incidental: deployed contracts sit behind access-managed proxies with role manifests and upgrade permissions routed through timelocks, multisigs, and a board and/or Security Council
The protocol exposes a real developer and operator stack, including audits, deployments, and open-source contract code, so it is better treated as reusable underwriting infrastructure than as a single insurance front end
Whitepaper: A canonical whitepaper PDF is available at ../whitepapers/ensuro-whitepaper.pdf; primary-source notes are in ../whitepapers/ensuro-primary-sources-2026-05-08.md.