Lifinity Lifinity oracle pricing
Lifinity’s decentralized exchange on Solana used an oracle as its main pricing reference. Its documented custom-oracle model required both a successful update in the current Solana slot and a sufficiently narrow confidence interval before trading. These conditions governed acceptable price data; separate service terms distinguished trader swap fees from project payments for Lifinity-supplied liquidity.
Updated ·
The protocol is winding down. Lifinity’s published notice sets December 31, 2026 as the deadline to claim all assets. All support, including its website, ends after that date.
Oracle Conditions and Pricing Parameters
| Parameter | Documented Meaning or Requirement |
|---|---|
| Primary Pricing Mechanism | Lifinity’s custom oracle supplied the main price reference. Pool asset balances weren’t the primary pricing mechanism. |
| Update Timing | In Lifinity’s documented custom-oracle model, trading required a successful update in the current Solana slot. |
| Confidence Interval | The interval had to be sufficiently narrow. No numerical cutoff accompanies the rule in Lifinity’s Oracle description. |
Concentration Factor
c
|
Multiplied the base constant-product parameter
k
to obtain the concentrated liquidity parameter
K
:
K = c * k
.
|
Rebalancing Price
p
|
The oracle-provided price of asset
x
entered Lifinity’s liquidity-adjustment equations.
|
The timing requirement addressed price freshness. The confidence interval separately constrained uncertainty around the price estimate. An update in the current slot satisfied only the timing requirement; the confidence condition still had to hold.
Reference Prices, Pool Depth, and Fees
Concentrated liquidity placed capital within a limited price range, adding trading depth there. The concentration factor described how the model scaled liquidity; it wasn’t a percentage charged on a trade. Likewise, the oracle’s confidence condition wasn’t a swap-fee rate.
The oracle reference also connected pricing to inventory management. Lifinity’s Rebalancing documentation described liquidity adjustments on each trade, oracle-price change, or both. Those adjustments changed liquidity as the pool sought balance. The overview’s description of delayed rebalancing concerned the market-making strategy; it didn’t relax the custom oracle’s current-slot trading requirement.
Lifinity documented two service models for projects requiring a custom oracle. In market making as a service (MMaaS), projects supplied the assets; Lifinity kept all trading fees, while projects retained any market-making profit. In liquidity as a service (LaaS), Lifinity supplied the assets and took on their price risk. Projects compensated Lifinity based on generated volume, using an asset of their choice. In a July 2022 Marinade governance discussion, Lifinity’s Durden distinguished a 0.12% trader swap fee in the Lido stSOL-USDC arrangement from Lido’s separate compensation of 0.05% of total generated volume, paid monthly. The swap fee was adjustable; neither historical rate establishes current charges. The oracle rules and concentration formula don’t specify a separate oracle-update charge or establish an all-in trading cost or cheaper execution. A reference price describes one input to pricing, while the amount received from a particular trade requires its actual execution terms.
Front-Running and Market-Making Outcomes
Lifinity’s Oracle description linked current-slot updates and sufficiently narrow confidence intervals to resistance against front-running, without quantifying the protection. Reducing impermanent loss was a stated aim of the wider market-making design. Meeting the oracle conditions didn’t establish a liquidity provider’s profit.
Pyth Integration and Custom Oracle Context
The June 20, 2024 Colosseum Codex listed Lifinity among applications using Pyth’s pull oracle on Solana. In Marinade’s July 15, 2022 governance discussion, Lifinity’s Durden described a proposed custom mSOL oracle based on Pyth’s SOL price feed. Pyth’s June 17, 2024 launch announcement later quoted him saying Lifinity had used Pyth since inception and was integrating its pull oracle for trade pricing. The mSOL proposal shows how custom oracle logic could use Pyth data. Neither statement establishes every pool’s configuration or whether the documented current-slot rule carried over unchanged.