Omnipair primary sources
Collected: 2026-05-11 UTC
Primary sources reviewed
- https://docs.omnipair.fi/
- Official documentation home
- Used to confirm Omnipair’s positioning as a permissionless, oracle-less, isolated-collateral margin protocol on Solana
- https://docs.omnipair.fi/llms.txt
- Official docs index
- Used to map the documentation structure and identify core mechanism, governance, and risk pages
- https://docs.omnipair.fi/omnipair/problem
- Official problem statement
- Used to confirm the target problem: long-tail leverage and lending without external oracle/risk-committee bottlenecks
- https://docs.omnipair.fi/omnipair/solution
- Official solution page
- Used to confirm the GAMM framing, unified swap-plus-lending pool design, and intended use cases for traders, LPs, and token projects
- https://docs.omnipair.fi/technical-breakdown/overview
- Official technical architecture overview
- Used to confirm reserve accounting, solvency invariants, double-EMA pricing, utilization-based rates, fee-surplus accounting, and recursive leverage framing
- https://docs.omnipair.fi/technical-breakdown/generalized-automated-market-maker
- Official GAMM mechanism page
- Used to confirm the virtual/cash/debt reserve split, state-transition equation, and the role of pessimistic pricing inside the AMM-native lending design
- https://docs.omnipair.fi/technical-breakdown/liquidations-debt-write-off
- Official liquidation and collateral-valuation page
- Used to confirm impact-aware collateral valuation, pessimistic reserve reconstruction, partial-versus-full liquidation logic, and debt write-off mechanics
- https://docs.omnipair.fi/technical-breakdown/slippage-aware-collateral-factor
- Official collateral-factor page
- Used to confirm dynamic CF computation, the 5% borrow-versus-liquidation buffer, and
applied_min_cf_bpsborrower protection
- https://docs.omnipair.fi/documentation/resources/security
- Official security page
- Used to confirm published audit references, fee-claim mechanism, futarchy authority powers, and emergency
global_reduce_only
- https://docs.omnipair.fi/documentation/resources/addresses
- Official addresses and access-control page
- Used to confirm present upgradeability, Squads multisig control, lack of current timelock, and deployed authority accounts
- https://docs.omnipair.fi/governance/what-is-omfg
- Official governance overview
- Used to confirm OMFG ownership-token framing and the stated role of futarchy over treasury and mint authority
- https://docs.omnipair.fi/governance/governance-model
- Official futarchy-authority page
- Used to confirm MetaDAO-style market governance framing and the scope of policy decisions intended for futarchy
- https://github.com/omnipair
- Official GitHub organization
- Used to confirm the public code surface, core repositories, and existence of the main Rust protocol repo and indexer
Notes
- Omnipair’s key mechanism is not simply
oracleless lending; it is the collapse of AMM pricing, credit capacity, liquidation recovery assumptions, and fee accounting into the same isolated pool. - The impact-aware collateral-factor design is the part most worth preserving. It makes borrowing capacity depend on the same curve that would absorb liquidation, which is a stronger comparison hook than a generic
uses EMA pricesdescription. - The double-EMA system matters because it exposes an internal pricing-control surface: who sets half-lives and conservative-price rules can effectively shape how permissive borrowing is for volatile long-tail assets.
- The governance docs are analytically important because Omnipair’s stated futarchy destination should not hide the current reality: upgrades and admin authority remain under a Squads multisig without a timelock.
- This entry belongs in the active corpus because it helps compare permissionless lending designs that move risk policy into pool-native math against designs that leave core control with oracle providers, listing committees, or external liquidation markets.