Lido DAO has introduced NEST, an onchain mechanism designed to connect protocol revenue more directly to purchases of its governance token, LDO. The system uses treasury surplus generated from staking revenue and executes buybacks programmatically rather than through manual intervention.

The launch continues a broader LDO alignment effort that the DAO set as a goal for 2025 and carried into 2026. According to Lido, NEST was built to keep the process transparent, permissionless and under DAO control, with parameters set and changeable through onchain votes.

Why the DAO chose an automated approach

Lido said the buyback design reflects the same governance principles it applies elsewhere in the protocol, including fully onchain upgrade votes, Dual Governance oversight for stETH holders, and optimistic Easy Track motions for routine treasury actions.

The DAO said it considered simpler alternatives but rejected them. Manual monthly buybacks were seen as introducing discretionary human intervention, while burning purchased LDO was described as a one-off signal rather than a lasting mechanism. A fixed revenue split was also ruled out because it could route funds to buybacks even when there was no real treasury surplus.

How NEST functions at launch

NEST, short for Network Economic Support Tokenomics, compares the DAO’s share of staking revenue with a preset operating baseline. When revenue exceeds that level, part of the surplus is earmarked for LDO purchases. At launch, the baseline is set at $40 million annualized, or about $109,000 per day, and 50% of the daily surplus is routed into the mechanism.

Execution is scheduled daily and is permissionless, with purchases made through CoW Swap using Stonks v2. The system starts in Treasury mode, under which the full daily allocation is converted into LDO and sent to the DAO treasury through an Aragon Agent contract.

Lido said NEST uses cumulative accounting rather than resetting day by day. That means surplus can build into a running balance over time, while a negative balance causes buybacks to stop automatically until revenue recovers.

Caps, liquidity mode and DAO control

The launch configuration includes a $50,000 daily cap and a $10 million cap measured over a rolling 365-day period. Lido said the daily limit is intended to contain exposure over a roughly six-day governance response window to about $300,000.

NEST was also designed with a second operating mode for thinner onchain liquidity conditions. In LP mode, the daily allocation is split in half, with one part used to buy LDO and the other wrapped into wstETH. Both sides would then be deposited as DAO-owned liquidity into a deployed Curve v2 NG pool, with a 2% price-drift limit on deposits. The system is not starting in that mode, and switching later would require another onchain vote.

The DAO can change all major parameters by vote. Lido also said the architecture could support additional revenue sources in the future, although the launch version tracks staking revenue only.

Risk controls and what happens next

Lido said the mechanism was built with safeguards for daily treasury spending. It said parameter changes require full onchain approval, price queries can be paused independently, and three separate pause domains exist for the system. If slashing or another revenue shock causes the tracked revenue source to fall to zero, buybacks pause automatically without further governance action.

The DAO also said assets acquired through NEST remain under DAO ownership, and anything outside the mechanism’s predefined paths would need explicit authorization. Backtesting on 2024 and 2025 revenue, according to Lido, showed the model would have spent $7.09 million out of $94.18 million in total rewards.

Lido separately noted that NEST is not the same as the LDO Accumulation Program approved on April 13, 2026. That earlier program was described as a one-time, discretionary treasury operation run by a committee, while NEST is positioned as a standing, rules-based mechanism. The next confirmed step is continued operation in Treasury mode unless the DAO later votes to change parameters or activate LP mode.

Source: blog.lido.fi