ipor-primary-sources-2026-05-13

IPOR primary sources

Collected: 2026-05-13 UTC

Primary sources reviewed

• https://docs.ipor.io/
  • Official documentation home
  • Used to confirm the current documentation split between Fusion branding, benchmark / derivatives docs, governance, and resources
• https://docs.ipor.io/resources/resources/research-and-whitepapers/ipor-conceptual-whitepaper
  • Official conceptual whitepaper page
  • Used to confirm the original benchmark thesis: a weighted inter-protocol offered rate designed to support DeFi fixed income and interest-rate derivatives
• https://docs.ipor.io/ipor-derivatives/automated-market-maker/ipor-swaps
  • Official swaps explainer
  • Used to confirm the pay-fixed / receive-floating and receive-fixed / pay-floating structure, LP pool counterparty model, fees, tenors, unwind path, and capped payoff logic
• https://docs.ipor.io/ipor-derivatives/developers-docs/ipor-oracle
  • Official oracle reference
  • Used to confirm the split between rate-calculation contract, oracle state contract, IBT accrual, asset/updater owner controls, and the mixed messaging around update permissions
• https://docs.ipor.io/ipor-derivatives/interest-rate-derivatives/ipor-publication
  • Official publication explainer
  • Used to confirm that publication cadence is governed by a heartbeat-style time / volatility / gas-sensitive threshold rather than by per-block updates
• https://docs.ipor.io/ipor-derivatives/automated-market-maker/risk-oracle
  • Official risk-oracle page
  • Used to confirm the offchain signed parameter path for leverage caps, collateral factors, dynamic offered-rate caps, and base spread parameters
• https://docs.ipor.io/ipor-derivatives/automated-market-maker/spread/math-behind-the-demand-spread
  • Official spread math page
  • Used to confirm that pricing depends on pool depth, collateral imbalance, time-weighted notional per leg, and DAO-configurable step-function spread policy
• https://docs.ipor.io/dao-governance
  • Official governance overview
  • Used to confirm the ongoing transition from legacy IPOR DAO toward Fusion DAO and the not-yet-launched $FUSN governance token
• https://docs.ipor.io/dao-governance/dao-governance/governing-multisig-wallets
  • Official multisig and timelock page
  • Used to confirm the still-concentrated governance and operations structure: DAO multisigs, timelock, treasury, oracle-fee, liquidity-mining, and operations wallets
• https://blog.ipor.io/ipor-protocol-architecture-overview-f9d35ac47ad
  • Official architecture article
  • Used to confirm the protocol’s decomposition into oracle, AMM, liquidity pool, asset-management, governance, monitoring, and API layers, as well as the explicit admission that publication is still fairly centralized
• https://raw.githubusercontent.com/IPOR-Labs/ipor-protocol/main/README.md
  • Public repo README
  • Used to confirm the project’s self-description as a benchmark-rate / derivatives / structured-products smart-contract system and to anchor the active codebase

Notes

• IPOR clears the intake bar because it is not just another fixed-rate UX layer or generic DeFi yield venue. It gives the corpus a useful lower-middle comparison point where benchmark construction, floating-rate accrual, fixed-rate quoting, LP underwriting, and governance are all explicit layers.
• The most reusable comparison hook is that IPOR bundles two usually separate things: a benchmark-rate oracle and an AMM for fixed-versus-floating interest-rate swaps. That makes it a useful bridge between oracle analysis and fixed-income derivative analysis.
• The strongest control-surface insight is the offchain dependence: benchmark publication, risk-parameter compilation, and governance operations are all operationally managed even though settlement and swap state live onchain.
• The docs expose a productive inconsistency worth remembering. Some text frames index updates as permissionless for anyone willing to pay gas, while the function table says update paths are whitelisted and the architecture writeup still describes publication as centralized. The correct analytical takeaway is not that one line must be ignored, but that publication authority remains an important governance dependency.
• The single-asset deployment pattern is also notable. The architecture writeup says contracts are deployed per ERC-20 asset for gas efficiency and reduced configurability, which is a useful contrast with more generic multi-asset derivative engines.
• No standalone official PDF whitepaper was confirmed in this pass; the official conceptual whitepaper appears to be hosted directly inside the docs site.