Equilibria
Equilibria pooled vePENDLE to boost rewards for Pendle liquidity providers
Equilibria connected Pendle liquidity deposits with pooled token locks to increase eligible rewards. Its original design linked liquidity providers, PENDLE holders, and ePENDLE staking through shared fees. Pendle has since replaced vePENDLE with sPENDLE, so that historical model doesn’t establish today’s rewards or deposit availability.
Liquidity deposits and token locks funded different parts of the system
The original arrangement joined two sources of capital: assets supplied to Pendle liquidity pools and PENDLE committed to voting power. Liquidity providers contributed pool positions. PENDLE holders supplied tokens that the protocol locked to obtain vote-escrowed PENDLE, called vePENDLE. Pooling those locks allowed depositors to benefit from boosting without each maintaining a personal vePENDLE position.
The relationship also ran in the other direction. A portion of the rewards generated through the platform supported fee sharing with ePENDLE stakers. That connected the demand for boosted liquidity rewards with the capital committed through PENDLE conversion.
These positions carried different exposures. A liquidity deposit remained tied to its underlying pool assets. Holding ePENDLE exposed its owner to the wrapper’s economics and market liquidity.
Pendle’s replacement of vePENDLE changed the starting point
Pendle now uses sPENDLE for its staking and governance system. Pendle paused new vePENDLE locks as part of the transition to sPENDLE. Existing locks received transitional treatment through virtual sPENDLE balances, with benefits tied to the locked position. That transition changed the mechanism on which the original booster depended. A description of accumulating fresh vePENDLE therefore belongs to the historical design, rather than an unconditional instruction for a new deposit. This upstream change alone doesn’t establish whether a particular Equilibria withdrawal or reward claim remains available.
A recorded position distinguishes a deposit from an approval
A wallet interaction can authorize spending, create a position, or collect an existing entitlement. Those actions have different outcomes. An approval grants a contract permission to move a token; it doesn’t by itself prove that a deposit occurred. For an existing position, the relevant starting record includes its chain, token identity, amount, and staking contract. A transaction receipt and the resulting contract balance provide stronger confirmation than a displayed yield estimate.
The original entry paths created different balances
Pendle liquidity positions
Liquidity deposits entered the pool reward system. Their accounting depended on the particular pool and the deposited position, rather than a personal PENDLE lock. A position balance identifies the stake; claimable rewards identify a separate entitlement. Combining the two obscures whether a transaction moved principal or paid earnings.
PENDLE conversion and ePENDLE staking
The conversion path issued a wrapper token against committed PENDLE. The original conversion mechanism issued ePENDLE at a 1:1 ratio to PENDLE converted. Staking that wrapper was a separate action that connected it to reward distribution. The issuance ratio described token creation; it didn’t promise an equivalent market exit.
Reward distribution separated accrual from payment
The legacy reward system collected earnings from Pendle and distributed the liquidity providers’ portion through a Streaming Payout Distributor. Deposits, withdrawals, and harvest calls could trigger collection. Distribution then depended on time and each depositor’s share of the pool, so a harvest didn’t simply pay every newly arrived depositor an immediate share of all earlier earnings. This also explains why an annualized display and an immediately claimable balance could differ. A claimable balance describes an accrued entitlement; an annualized percentage expresses a rate under particular assumptions.
Fees and emissions require their own time scope
The fee structure dated December 22, 2024, applied a 22.5% protocol fee to boosted LP yield. That denominator matters: the percentage described a charge on the specified earnings, rather than a deduction of the same percentage from deposited principal. The allocation supported ePENDLE stakers, treasury functions, and other specified protocol uses. It’s a historical schedule, not a permanent price for every operation.
EIP-6 halted EQB and xEQB emissions for Pendle liquidity providers on Equilibria. Earlier descriptions of token incentives therefore can’t establish an ongoing reward stream. Network transaction fees remain a separate cost from protocol performance fees. Where an operation includes a swap, the exchange fee and price impact also affect its outcome. Adding an old incentive rate to a newer fee schedule would combine incompatible assumptions.
Direct Pendle positions and wrapper holdings have different commitments
A direct liquidity position keeps the pool exposure without adding Equilibria’s deposit and reward accounting. The original booster added pooled voting power and a performance fee arrangement. Comparing those paths requires the same underlying pool, the same observation period, and compatible definitions of earnings. An advertised historical boost can’t settle that comparison after the upstream incentive mechanism changes.
PENDLE staking and ePENDLE ownership also involve different contracts. The former can enter Pendle’s native sPENDLE system under its participation and withdrawal rules. The latter remains a separate wrapper holding. Native staking terms don’t automatically become redemption terms for ePENDLE. In particular, a protocol’s underlying assets and a holder’s immediately transferable wallet balance are different quantities.
An unstaking example ends with an observable wallet balance
Consider a hypothetical existing ePENDLE stake. Assume its contract permits unstaking, the wallet has enough native currency for the transaction, and the selected ePENDLE-to-PENDLE swap currently has no executable quote. These conditions describe this example only. The holder records the staked amount and wallet balance before submitting the supported unstaking action. The intended first result is transferable ePENDLE, which keeps the withdrawal separate from a market sale.
After confirmation, the receipt must show a successful transaction, and the holder’s staked balance recorded in the contract must reflect the withdrawal. The wallet’s ePENDLE increase should reconcile with the amount that the transaction returned. Those observations establish completion even though the intended PENDLE sale remains unavailable. A reward estimate doesn’t provide that confirmation, and repeatedly submitting the withdrawal wouldn’t resolve the unavailable swap quote.
The holder stops with ePENDLE in the wallet and leaves the unquoted swap unsubmitted. The completed transaction incurs its actual network cost. A later sale would add the costs and price impact of its executable quote. This example finishes with recovered control of the wrapper tokens; it doesn’t assume a sale price, successful redemption, or future reward.
Exit liquidity and governance distributions remain separate
The original ePENDLE exit mechanism relied on exchanging the wrapper for PENDLE in a liquidity pool. Available liquidity and the market exchange rate governed that sale. Unstaking alone didn’t reverse the original PENDLE commitment. A treasury distribution follows a different process: its applicable allocation, eligibility conditions, and execution must establish what a holder receives. A governance proposal or treasury asset balance doesn’t itself place spendable tokens in that holder’s wallet. For any completed exit, the decisive record is the asset and amount actually received, reconciled against the position that the transaction reduced.
Before you start with Equilibria
Does buying EQB give me the same position as holding ePENDLE?
EQB and ePENDLE represent different parts of the protocol. EQB is its governance token, while ePENDLE originated as the tokenized counterpart of PENDLE committed through the wrapper mechanism. Buying EQB doesn’t create an ePENDLE staking balance. Any distribution involving both groups needs its own allocation and eligibility rules; the tokens aren’t interchangeable.
Why can ePENDLE trade below the amount of PENDLE originally converted?
Its market exchange rate reflects the liquidity and demand available for selling the wrapper. The original issuance ratio didn’t guarantee that buyers would pay the same amount of PENDLE later. Expectations about rewards, access to underlying assets, and governance decisions can also affect demand. A discount therefore doesn’t, by itself, establish a token accounting error.
Can a Pendle liquidity position have a different maturity from another position?
Pendle markets can have different maturity dates, so the exact market is part of a position’s identity. A matching asset name doesn’t establish that two liquidity positions belong to the same market. Maturity also matters when interpreting remaining yield exposure and available withdrawal assets. The position’s market details take precedence over a broad protocol label.
Do I need another PENDLE conversion to collect an existing reward?
A new PENDLE conversion doesn’t establish entitlement to an already accrued reward. That entitlement belongs to the relevant position and distribution mechanism. A claim may require a network transaction and its fee, but those costs are separate from buying or converting more principal. An unavailable claim needs an explanation tied to its contract or distribution state.
What happens to transaction costs if an attempted operation reverts?
An on-chain transaction that reverts can still consume gas even though it doesn’t complete the intended operation. A wallet rejection before submission is different because no transaction reaches the chain. When reconciling a failed attempt, separate the native currency spent on execution from the token balance that the attempted deposit, withdrawal, or swap was meant to change.
Last updated: