Skip to content

Capital Structure

Chronomancy’s capital structure is designed to minimize the external raise required while offering competitive yields to both retail and institutional capital. Three mechanisms reduce capital dependency: junior tranching, protocol-owned liquidity, and CS-driven risk segmentation.


Both the FF vault and the Rewind insurance pool use a two-tranche structure:

TrancheFunded ByRisk ExposureTarget Yield
Junior$CHRONO stakersFirst-loss — absorbs drawdowns before senior capital is affected25–40% APY
SeniorExternal USDC LPs or institutional raiseProtected — last to take losses3–8% APY

Why this matters for the raise: If $CHRONO stakers provide 30–50% of the pool capital as first-loss junior capital, the external raise requirement drops by the same proportion. A $500K insurance pool only needs $250–350K from external investors — the rest is funded by the community.

Why stakers accept first-loss risk: The 25–40% APY on junior capital is substantially higher than the 3–8% senior yield. This is the standard structured finance trade-off: higher yield in exchange for higher risk. The difference from traditional structured products is that the junior holders are protocol stakeholders who have direct visibility into the risk.


The core insight: $CHRONO stakers are already holding the token for yield and protocol access. Routing some of that staking into the junior tranche converts passive token holding into active protocol capitalization.

This creates a flywheel:

  1. Protocol revenue grows → junior stakers earn more APY
  2. Higher APY attracts more $CHRONO stakers
  3. More junior capital → more insurance capacity + larger FF vault
  4. More capacity → more users insured/exited → more revenue

The community-funded balance sheet cuts the external raise by 30–50% compared to a protocol that relies entirely on institutional capital. It also aligns the community’s financial interest with the protocol’s solvency — junior stakers have direct incentive to monitor pool health.


The protocol’s most structurally elegant capital efficiency hack: Chrono Score functions as a per-user credit score that lets the protocol serve the same capital base across more users.

Standard insurance pools size capital for the worst-case scenario across all users. But Chronomancy knows, per user, how likely they are to claim:

CS BandClaims FrequencyCapital Required Per Policy
A (Premium)18–22%Low — most policies never claimed
B (Standard)25–30%Moderate
C (Basic)30–35%Moderate–high
D (Unscored)40–50%High

By pricing each band separately, the pool avoids cross-subsidizing high-risk users with capital reserved for low-risk users. This enables:

  • Gearing ratio improvement: The same $1M pool can cover 2–3× more total insured value if it’s efficiently segmented by CS band
  • External investor pitch: “Our insurance pool has actuarially segmented risk — Band A customers are near-zero claims risk, Band D are priced to be profitable on their own”

This is precisely how auto insurance works: good drivers subsidize bad drivers in undifferentiated pools. Chronomancy is the prediction market equivalent of usage-based insurance.


ComponentMinimumComfortable
FF vault seed$50K$250K
Insurance pool (senior)$100K$300K
Insurance pool (junior, from stakers)$50K$200K
Total external raise needed$175K$570K
With community junior tranche$125K$350K

The $420K–985K total raise figure (from the Build Roadmap) includes engineering costs, audits, and legal — not just capital. The raw capital requirement for the pools is more modest.

Related:

  • Staking — how $CHRONO stakers participate in the junior tranche
  • Rewind — insurance pool architecture in detail
  • Financial Model — scenario-by-scenario capital assumptions