Summary: Re is best understood as a tokenized feeder structure into licensed reinsurance balance sheets rather than as a mutual or discretionary onchain claims market. Its primary docs center the mechanism on Insurance Capital Layers (ICLs) that mint senior reUSD and junior reUSDe, sweep idle assets into Fireblocks custody, and allow capital to leave only when a legally binding Surplus Note is signed with a licensed reinsurer. Offchain balances in trust or operating accounts are then attested daily by The Network Firm and published via Chainlink. The reusable insight is that Re pushes insurance trust away from open claims governance and toward legal wrappers, actuarial reserve releases, licensed-carrier equity, and MPC-governed custody/oracle controls.
What it does:
Lets users deposit stablecoins into dedicated Insurance Capital Layers that mint either senior reUSD or junior reUSDe
Routes protocol capital into fully collateralized quota-share reinsurance exposure through licensed insurers and Surplus Notes
Uses §114 trust accounts, Fireblocks custody vaults, and daily proof-style reserve reporting to mirror offchain collateral back onchain
Offers different redemption paths: reUSD targets instant liquidity when buffers are available, while reUSDe uses quarterly windows tied to surplus release
Packages reinsurance-backed yield into ERC-20 tokens intended to remain composable across DeFi venues such as Curve, Pendle, and Morpho
Key claims:
The docs describe ICLs as vaults with one token per tranche, making the token structure itself the main control surface for senior versus junior insurance-capital exposure
Capital can leave an ICL only through the Surplus Note gateway, which means practical authority over deployment sits in the legal agreement path with a licensed reinsurer rather than in a purely onchain allocation loop
Re’s loss waterfall is explicit: reinsurer equity absorbs losses first, then reUSDe, then reUSD; this makes the protocol closer to a structured reinsurance feeder or sidecar than to a shared-capital mutual
The protocol’s transparency claim depends on daily attestations by The Network Firm and Chainlink publication of offchain balances, so trust is reduced but not eliminated; it shifts into an attestation-and-oracle stack rather than disappearing
Governance and operations are intentionally permissioned: minting/redemptions require KYC/AML, upgrades use MPC-controlled UUPS contracts with a 48-hour timelock, and docs describe an expert-led council overseeing allocation and risk management
As a comparison class, Re is valuable because it shows a distinct insurance architecture from Etherisc, Ensuro, Nayms, Nexus Mutual, Cozy, and Risk Harbor: not framework tooling, not mutual-wide claims voting, not protocol-local safety modules, and not automated parametric swaps, but an onchain wrapper around regulated reinsurance deployment
Whitepaper: No canonical standalone whitepaper surfaced in this pass. The strongest primary materials were the official docs, FAQ, risk-management, and security pages; see ../whitepapers/re-primary-sources-2026-05-08.md.