RLD Protocol primary sources
Collected: 2026-05-12 UTC
Primary sources reviewed
- https://docs.rld.fi/
- Official documentation home
- Used to confirm the protocol’s top-level split between trader docs, builder docs, and research / whitepaper-style materials
- https://docs.rld.fi/research/executive-summary
- Official executive summary
- Used to confirm the protocol’s core framing around rate-level perpetuals, synthetic bonds, GhostRouter/TWAMM execution, amortizing perpetual options, and parametric CDS
- https://docs.rld.fi/research/parametric-cds
- Official research page for Parametric Credit Default Swaps
- Used to confirm the core mechanism claim: lending-pool interest-rate spikes are treated as deterministic solvency oracles for fully collateralized, zero-discretion CDS-style coverage
- https://docs.rld.fi/traders/credit-default-swaps
- Official trader-facing CDS explainer
- Used to confirm how the protocol describes coverage purchase, underwriting, continuous premium flows, rate-triggered payout behavior, and the specific risk events it wants to wrap
- https://docs.rld.fi/developers/architecture
- Official architecture reference
- Used to confirm the singleton
RLDCore, prime-broker account model, position-token design, pluggable oracle/funding/liquidation modules, and GhostRouter / TWAMM execution stack
Notes
- RLD clears the intake bar because it is not merely another mutual-style claims pool. Its strongest mechanism claim is that algorithmic interest-rate spikes in lending markets can be turned into a continuous, objective insurance trigger and also into a broader fixed-income derivative index.
- The most reusable comparison hook is the split between hidden default insurance inside passive lending yield and explicit tail-risk pricing through parametric CDS underwriting.
- The protocol is also useful because it joins several layers that are often filed separately: rate speculation, fixed-yield packaging, solvency insurance, broker-account margining, and execution routing.
- The current public materials are research-heavy and architecture-heavy. They are rich enough for mechanism analysis, but they should still be treated as first-party design and positioning documents rather than as independent proof of market adoption or performance.
- No standalone whitepaper PDF was confirmed in this pass.