RE: LeoThread 2026-01-20 14-38

You are viewing a single comment's thread:

A new ACE tool is going live today

You will be able to single-side stake yoru ACE. Single-side staking your ACE allows you to earn yield on it

Yield is generated in two ways:

  1. Real-yield from the LP's
  2. A 10% boosted yield added on top of that

Our modeling estimates that LPs should pay ~10-30% APR. Assuming a modest 10% APR + the boost of 10% APR for buying the presale, your total yield for single-side staking ACE should be 20% or higher



0
0
0.000
5 comments
avatar

This does not affect the incentive to bring liqueness to the LP? Why risk an impermanent loss if I can do this instead?

0
0
0.000
avatar

It is effectively the same thing but only can apply to the stablecoin LPs. So if you want to add liquidity to ACE-LEO (for example), you still have to do that on your own

In the event you have ACE and want to LP with stablecoins, you can single-side stake and we will basically LP it for you (automatically through the PSM Treasury)

This works very similarly to curve gauges. #askleo can you explain how curve gague single sided staking works for stabelcoin LPs?

0
0
0.000
avatar

Curve's gauge system incentivizes liquidity provision in specific pools via CRV emissions, allocated based on votes from veCRV holders (locked CRV). For stablecoin LPs like 3pool (USDC/USDT/DAI), it enables single-sided staking: users deposit one stablecoin, and the protocol uses internal balancing (via liquidity swaps within the pool) to simulate full LP position without needing paired assets from the user.

This avoids impermanent loss risk for stables (minimal volatility) while earning fees + gauge rewards. Earned CRV can be boosted up to 2.5x by locking into veCRV. Gauges are pool-specific; voting directs more emissions to desired LPs.

For ACE, this mirrors by automating LP via PSM for single-sided deposits, capturing stable yields without manual pairing.

NOTICE: Rafiki is still in early training and may occasionally provide incorrect information. Please report errors using #feedback

0
0
0.000