Amulet

  • Name: Amulet
  • URL: https://amulet.org/
  • Category: decentralized insurance-adjacent protocol / RiskFi yield-protection stack / parametric underwriting infrastructure
  • Tags: solana-ecosystem
  • Summary: Amulet is best understood as a hybrid of a yield router and an insurance-like risk-transfer protocol, not as a classic mutual. Its current docs frame the product around “RiskFi”: users pursue third-party yield while Amulet embeds protection into vaults, prices specific risks, allocates limited Amulet Safety Fund capacity, and triggers payouts through parametric checks like Current Price < Trigger Price. The especially reusable mechanism is that Amulet moves protection away from broad discretionary claims committees and into vault-level stop-loss logic, product-tier capacity formulas, and underwriting capital backed by liquid-staking assets plus future-yield claims.
  • What it does:
    • Offers yield strategies with built-in loss protection through products like AmuShield rather than selling only standalone cover policies
    • Splits the system into yield vaults, risk vaults / underwriting capacity, parametric claim checks, and a safety fund that absorbs some covered losses
    • Uses a synthetic underwriting token, aUWT, backed by selected Solana liquid-staking tokens and protocol revenue-sharing mechanics
    • Prices cover using protocol-specific ratings, APY context, and supply-demand / capacity conditions rather than a flat mutual premium schedule
    • Uses vault suspension plus emergency asset retrieval when trigger conditions are met, then pays any remaining compensation from the Amulet Safety Fund subject to capacity limits
  • Key claims:
    • The Amulet V2 whitepaper explicitly frames the protocol as a “RiskFi” platform that combines yield opportunities with risk management and built-in loss protection
    • The same whitepaper says users interact through paired yield and risk vaults, with generated rewards periodically used to buy or renew protection and parametric checks deciding when claims are made
    • The pricing-model docs say Amulet prices products from protocol ratings, APY context, and supply-demand conditions, which means underwriting discretion lives in Amulet’s risk-modeling and capacity-management layer rather than in a single open mutual pool
    • The risk-management docs describe shared common underwriting pools, product-specific underwriting pools, concentration caps, and Solvency-II-inspired reserve logic, making capital allocation a central control surface
    • The aUWT docs show underwriting capital is tokenized into a synthetic claim on staked SOL-derivative collateral plus protocol revenues, and that Amulet can mint aUWT debt backed by near-term future yields to finance claims
    • The AmuShield and Amulet Safety Fund docs show that claim handling is meant to be parametric and sequential: suspend the vault, retrieve residual assets, then pay any remaining compensation up to the vault’s allocated capacity
    • The AMU token docs show governance exists, but also explicitly disclaim legal control over company matters, which is useful when distinguishing protocol-level token governance from offchain organizational control
  • Whitepaper: Amulet hosts a canonical V2 whitepaper in docs and a standalone litepaper PDF; a local copy of the litepaper is saved at ../whitepapers/amulet-litepaper.pdf. See also ../whitepapers/amulet-primary-sources-2026-05-08.md.
  • Sources:

Internal linkages

  • Best insurance-style comparison: nexus-mutual
  • Best underwriting-mechanics comparison: risk-protocol
  • Best collateral-and-operator contrast for the staking side of the stack: stakewise

Control surface

  • The interesting power is not in the word insurance. It sits in product ratings, capacity formulas, trigger definitions, vault suspension rules, safety-fund allocation, and the quality of the liquid-staking collateral beneath the underwriting side.

  • That is why Amulet is worth keeping: it packages yield routing and parametric protection into one operator-shaped risk stack instead of acting like a plain mutual.

  • Last reviewed: 2026-06-01 UTC