NEST: tying the buyback threshold to the approved budget

Hi all,

NEST has been live since 10 August (launch thread) and has not bought a single LDO yet. Its budget counter stood at −$542,451 at the end of September and keeps falling on most days. I spent the last few weeks building a full model of the mechanism to understand whether this can be fixed by tuning parameters. Parameter tuning alone does not solve it. The model points instead to the budget and to how profit is defined as the main levers. Below is what I propose, followed by the reasoning. The full report, model and data are linked at the end.

What I propose

Step 1. Now, through votes, no contract changes

1. Cut the Foundations budget for 2027 materially and, in the same vote, set the NEST threshold equal to the approved budget. I am asking for around $30M, about 30% below the current $43.8M. In the model, buybacks start to grow meaningfully from a cut of about 20% (roughly $35M), and a 30% cut roughly doubles them compared with today. The approved Foundations budget would serve as the operating baseline, not as a claim that it captures every DAO outflow; material off-budget spending, such as the $6.06M Kelp-related costs, would need to be reflected separately.

2. Change the threshold only together with the budget. Any increase in spending, during the year or in the next budget, comes as a separate proposal that explains what the money is for and what it delivers, and the threshold rises with it.

3. Keep the surplus share at 50% until a true-up against actual expenses is in place (item 8 below).

4. Publish budget requests with a breakdown by main line items and an estimate of NEST buybacks at that level of spending, and publish quarterly expense reports faster with the same breakdown.

5. Give NEST its own Easy Track top-up program, separate from the limit used for expense payments.

6. Do not use NEST-bought LDO for contributor payouts. Otherwise distributions eat the buybacks. Whether the tokens are burned or locked is a separate decision for the DAO.

Step 2. In parallel, in development

7. Connect additional DAO income that NEST does not currently capture. Treasury income and Earn appear to add roughly $3.3M a year at the H1 2026 run rate. CSM rebates may add further income, but their accounting treatment relative to reported net staking revenue should be confirmed first. The threshold would also need adjusting for referral payouts, which NEST counts before deduction.

Step 3. Later, if the DAO decides

8. A new allocator with a quarterly true-up against actual expenses. It would keep accruing 50% of the daily surplus, then replace that with the actual quarterly result once the report is out: 75% of a quarterly profit goes to buybacks, and a quarterly loss goes into the deficit in full. This is the point where the share of real profit going to buybacks can rise above 50%.

Why

NEST is not buying because staking revenue is below the $40M reserve. With the current module set, the threshold is covered only when ETH is above roughly $2,668, and every weaker day adds to the deficit. The four days between activation and connecting the revenue source added $147,658 to it, but that is a secondary factor.

The accumulated deficit makes this worse. Every dollar of it has to be earned back before NEST can buy anything. At a constant ETH price of $2,700, roughly where it is now, the model has the first purchase 838 days away, about 2.3 years. At $2,680 it is about 6.3 years, and below roughly $2,668 the deficit only grows. Across random ETH price paths, NEST makes at least one purchase in the next 12 months in only about half of the scenarios. ETH rallying would fix this, but that is not something the DAO controls. The one lever it does control, without weakening the protection the mechanism is built on, is expenses. With the threshold at a $30M budget and ETH at $2,700, the same deficit would be paid off in about 40 days.

Tuning the numbers in the current contract does not solve this. A lower threshold or a higher share buys more, but it also raises the share of purchases made in years the DAO ends at a loss. A $30M threshold with a 100% share at current expenses gives about $6.9M of buybacks a year while the DAO’s profit before buybacks is only about $1.3M, and more than half of those purchases land in loss-making years. That is spending the treasury, not distributing profit.

The only sustainable way to increase buybacks is more income or lower expenses. But today savings never reach buybacks, because the threshold is a fixed $40M unrelated to the DAO’s actual budget. Cut expenses by 10%, 20% or 30% and NEST still buys about $2.15M a year in the model. Once the threshold equals the approved budget, that changes:

Expenses Buybacks, threshold = budget Share of purchases in loss-making years DAO profit before buybacks
as now ($43.8M) $1.58M 5% about $1M
−10% $2.25M 6% about $5M
−20% $3.14M 8% about $9M
−30% (about $30M) $4.28M 5% about $13M

A 10% cut barely changes buybacks; the effect becomes meaningful from about 20%. Buybacks grow here because there is real profit left after expenses, not because NEST splits the surplus more aggressively.

The 50% share matters for the same reason. The current contract sees only the approved budget, not actual spending, so a 100% share leaves no buffer if expenses run over or revenue falls during the year. At a $30M budget, 100% would give about $5.63M of buybacks but more than double the share of purchases in loss-making years. With a true-up in place, the report suggests 75% of actual profit rather than 100%.

On top of that, the allocator currently holds about 41 stETH, roughly two days of purchases, so even a positive budget would run dry quickly without a top-up rule.

How I checked this

I reproduced the allocator logic from the verified contracts and matched it against 32 on-chain budget recalculations to the dollar. I rebuilt the treasury’s staking fee series since January 2024 from rebase events and Chainlink prices at each block and reconciled it with Lido’s financial reports. On that series I ran the current rule and dozens of alternatives on history and 12 months forward across thousands of ETH price paths, plus stress scenarios with expense overruns, one-off losses and late reports. The report goes through 19 questions in detail.

Why now

Last year the budget request was posted in early December and voted on mid-month. If the threshold follows the budget, the 2027 request is the natural place to agree on it, ideally in the same vote. I would rather discuss this before the request is drafted than after.

Questions for the team

1. Why does NEST not count CSM rebates and other treasury income, and are revenue sources planned for them?

2. Are CSM rebates included in reported net staking revenue, and how much were referral payouts in H1 2026?

3. How is NEST meant to be topped up, and why does it share an Easy Track limit with expense payments?

4. What is planned for the purchased LDO, and will the liquidity mode be used?

5. Was it expected at launch that the mechanism would build a deficit for four days with no revenue?

6. Could quarterly expense reports come out faster and with a breakdown by main line items?

7. Which vote and which role would change the threshold parameter?

Materials

Full report: lido-nest-analysis/NEST_report.md at main · 0xkzmch/lido-nest-analysis · GitHub

Model, scripts and data: GitHub - 0xkzmch/lido-nest-analysis · GitHub

All figures are model scenarios under the revenue, expense and market assumptions described in the report, not forecasts. The model does not try to predict the effect of buybacks on the LDO price, and the revenue base reflects the current set of staking modules. Happy to walk through any part of it and to rerun the numbers with other assumptions.

11 Likes

Hi Kuzmich

Thank you for this detailed and data-driven analysis.

Regarding item 6 (“Do not use NEST-bought LDO for contributor payouts.”), I would like to propose a definitive rule: all LDO tokens purchased by the NEST mechanism must be permanently and programmatically burned,as all another projects already made m

Why this matters:

1. True Deflationary Support: Merely locking the tokens in the Treasury leaves the door open for future distributions, which creates lingering selling pressure in the eyes of the market. Permanent burning reduces the total supply irrevocably.

2. Direct Value Alignment: A strict burning mechanism guarantees that every dollar saved from expense optimization directly boosts the scarcity of LDO, aligning the interests of long-term holders and governance participants.

5 Likes

Thanks, I agree. I left burn vs lock open in the post only because I didn’t want the burn question to block the rest, but my own preference is burning.

Locking leaves the decision open forever, and the market prices that in. Burning closes it. It also makes the link you describe very direct: every dollar the DAO saves on expenses ends up as LDO taken out of supply for good, not parked in the treasury until the next budget needs it.

Two things worth being realistic about. First, the volumes. Even with expenses cut by 30%, the model has NEST buying roughly 1.7% of the LDO outside DAO and Foundations holdings per year, around 0.6% at current expenses. So burning makes the policy credible, but the supply effect will be gradual. Second, the mechanics. Right now the purchased LDO goes to the treasury, so a programmatic burn needs either a change to where the executor sends tokens or a recurring burn through governance. I’d like the team to say which is cleaner and whether LDO’s token controller makes this straightforward.

If others support it, I’m happy to change item 6 to an explicit burn.

5 Likes

It is better than nothing (which is the current situation). Other companies are already actively and successfully adapting to current market realities with burn mechanism, delivering results, and creating new revenue-generating mechanisms.

5 Likes

First, this is good work, and thank you for modeling the mechanism end-to-end rather than just reacting to the counter. The timing is right: raising this now, before the 2027 budget request is drafted, is exactly when a change like linking the threshold to the budget can make it into the request rather than waiting a full cycle. Some of what you propose I think is right, and I’ll flag it to the team. On the rest, I either see it differently or want you to tighten the argument. Going through it in order.

Step 1

Tying the threshold to the approved budget. I agree, and I think it belongs in the Grant request vote itself. I’ll raise it with the team; the 2027 request is the natural place to settle this, ideally in the same vote, exactly as you suggest.

The size of the cut (~30% / ~$30M). The logic is clear, and I follow it. But a number like that has to come out of actual bottoms-up planning, not the model alone, which is exactly what the budget request is for. So specific figure TBD.

A separate Easy Track top-up program for NEST. At first glance, this reads as a no-brainer, but the shared limit was a deliberate resource-optimization decision, not an oversight. We don’t see the $10M limit as binding within the existing TMC Easy Track. It is a limitation in the sense that it is a shared ET with TMC and any selling of stETH or swaps. Therefore scaling is capped but should be sufficient for $10M. If you think NEST needs its own program, it would help to explain why the current limit is a real constraint.

Not using NEST-bought LDO for contributors’ grants. I want to make sure I understand the concern because I don’t think the silent-distribution path you’re worried about exists. If the DAO approves contributor grants in LDO, that appears in a grant request or separate proposal. The current contributor program (TRP, 22M LDO allocated from treasury) ends October 31. Any further treasury LDOs for contributors will be visible in a grant request. There’s no mechanism to quietly pull LDO from the treasury; it’s always a public move.

Step 2

Connecting additional DAO income NEST doesn’t capture. This was always part of the plan. The mechanism was built to be modular, so new sources can be added as it grows. It makes sense to wire them in once revenue from newer lines is material enough to be worth it. Right now most of it is still ramping, relatively immaterial compared with revenue (~$1.3m for H1).
One caveat: treasury operations aren’t Included because those include substantial exchange losses on stETH, which make total treasury income negative. Even with all contributions made.

Separately, and this is my own flag, not part of your proposal, we should look at whether the cumulative counter resets at the year boundary. There are arguments on both sides, and I want to bring it up for consideration on the research forum.

On your questions, here’s what I can answer now:

  1. Why NEST counts only staking revenue. Staking is by far the largest source. The others are still ramping or effectively zero. As above, the mechanism was built to be modular so sources can be added as they grow. This is a start-with-what-matters choice, not an oversight.

  2. Whether CSM rebates are in reported net staking revenue / referral payouts in H1. CSM rebates are included in financial reporting, but they are not counted by NEST; they reach the Treasury as separate monthly transfers rather than through the on-chain staking fee NEST reads (recently ~30–34 stETH/month; 161.54 stETH in H1 2026, ~294 stETH YTD through September).

  3. How NEST is topped up and why it shares an Easy Track limit. It is on one of the existing Easy Track (TMC one) and has already been topped up once, so fully ready for the first buyback. As above, the shared limit was a deliberate optimization, and we don’t see it as insufficient for at least this year. If you have a specific concern, I’d like to understand it.

  4. What’s planned for the purchased LDO, and will liquidity mode be used? No specific plans for the purchased LDO. On liquidity mode, there are a few blockers. One is a depth check: at current levels, liquidity mode doesn’t grow LDO liquidity on the market, which was the point of building it. It may be proposed to the DAO later, but it won’t be used without an explicit DAO decision.

  5. Was the four-day deficit expected at launch? Yes it follows from the technical limitations of the launch. And given how long ETH sat at low prices before NEST went live this year, it’s more or less fair.

  6. Which vote and role would change the threshold? The threshold parameter is gated behind DEFAULT_ADMIN_ROLE, which is held by the Voting contract. Changing it requires an on-chain vote.

Again, useful and well-argued. I’d rather settle the budget–threshold link in this year’s request than leave it for the next cycle.

4 Likes

Thanks, Jenya, this is really helpful, and good to hear the budget link can go into the 2027 grant request itself. That was the main point.

On the size of the cut, agreed, the figure should come from bottoms-up planning. I’d suggest one thing about how that planning is structured. Budgets across DAOs tend to bundle running costs and new initiatives into one number, and once it’s approved there’s rarely a way for tokenholders to check what each part delivered. It would help if the 2027 request separated a base budget, what it takes to run and maintain the protocol, from new initiatives. The base budget would set the NEST threshold. Each new initiative would come as its own proposal with a cost, a goal and a few metrics to review after six or twelve months, and the threshold would rise only by what the DAO actually approves. That way the DAO can see what it’s paying for, judge whether it worked, and the trade-off against buybacks stays visible for every decision. The model can also show expected buybacks and DAO profit for whatever base budget the request lands on, and I think that table belongs in the request too.

On Easy Track, fair on the size for this year. My concern is less the cap than the trigger. Top-ups are manual motions, and the allocator holds roughly two days of purchases at the daily cap, so once the budget turns positive, buybacks pause until someone submits the next motion. A simple rule would solve it without a separate program, for example topping up monthly to the smaller of the positive budget or about 30 days of the cap.

On contributor LDO, I didn’t mean anything silent, and it’s right that grants are always public. The point is that NEST-bought LDO lands in the same treasury pool future LDO grants come from, so buybacks and grants net against each other. Since there are no plans for the purchased tokens yet, I’d suggest the DAO picks an explicit policy, either burning them, as suggested above in the thread, or keeping them separately accounted and excluded from grants.

Thanks for the correction on treasury income, I’ll drop it from the list. CSM rebates at 30–34 stETH a month are roughly $1M a year, comparable to Earn, so they may be the first source worth wiring in. Confirming they’re already in reported revenue also settles one of my open assumptions.

Thanks also for the direct answers. Agreed that liquidity mode should stay off without an explicit DAO decision, and the four-day gap at launch is fine as explained. Since the threshold sits behind DEFAULT_ADMIN_ROLE on Voting, it would be good to plan the threshold change into the same on-chain package that follows the grant request vote, so the budget and the threshold take effect together.

On a yearly reset of the counter, I modelled deficit write-offs in the report (point 7). They buy more, but the share of purchases made in years the DAO ends at a loss rises noticeably, from about 12% to about 29% for a quarterly reset. I haven’t run a yearly reset over a multi-year horizon yet and can do that for the discussion.

4 Likes

Hi! I reran the model with the two corrections from the thread. CSM rebates are no longer added to DAO profit on top of reported revenue, and I now show DAO profit in two versions, with treasury income as in the report and with treasury income set to zero. Since that line can turn negative, the zero case is the more cautious one, and if it is actually negative the profit figures would be lower still. Buybacks do not depend on this assumption, because NEST does not see treasury income at all, so only the profit and risk columns change between the two versions. Below are the two calculations discussed above, a budget table and a yearly reset of the NEST counter.

1. Buybacks at different budgets, with the threshold equal to the budget

Share stays at 50%, the starting deficit is the actual −$542,451, and the horizon is 12 months from 1 October 2026 across 1,000 ETH price paths. Actual expenses are assumed to match the approved budget.

The average is taken over all 1,000 scenarios, including those with no purchases at all, so it should not be read as what NEST will buy in a normal year. It is pulled up by the scenarios where ETH rises and NEST buys a lot. That is why I also show the median, the outcome of a typical year, and the chance of making any purchase. At the current budget the median is zero, meaning that in most scenarios NEST buys nothing over the next 12 months, and the $1.74M average comes entirely from the stronger ETH paths. Around $35M the median turns clearly positive, and at $30M a typical year already brings about $3.2M of buybacks.

Budget = threshold Average buybacks Buybacks in a typical year (median) Chance of any purchase DAO profit before buybacks, with / without treasury income Share of purchases in loss-making years, with / without treasury income
$43.8M (as now) $1.74M $0 36% $1.0M / −$1.8M 7% / 10%
$40M $2.32M $0 47% $4.5M / $1.7M 4% / 12%
$38M $2.69M $0.39M 56% $6.3M / $3.5M 7% / 13%
$35M $3.35M $1.26M 69% $9.0M / $6.2M 7% / 15%
$32M $4.13M $2.35M 82% $11.8M / $8.9M 7% / 14%
$30M $4.71M $3.18M 89% $13.6M / $10.8M 6% / 13%
Current NEST ($40M threshold, $43.8M spending) $2.32M $0 47% $1.0M / −$1.8M 14% / 26%

Every $2M taken out of the budget adds roughly $0.3–0.6M of buybacks a year, and the effect grows as the budget gets smaller. The $40M row buys exactly as much as NEST does today, but with a much smaller share of purchases in loss-making years, because the threshold then matches what the DAO actually spends. Without treasury income the picture gets stricter, but the conclusion stays the same. At the current budget the DAO is slightly in the red before any buybacks, and today’s NEST makes about a quarter of its purchases in loss-making years. With the threshold equal to the budget that share is roughly half as large at any level of spending, and the cut to $30M still leaves about $10.8M of profit.

I think a table like this belongs in the 2027 budget request itself, so delegates can see what each level of spending means for buybacks at the moment they vote on it.

2. Yearly reset of the counter

Here I kept the current $40M threshold and 50% share and compared three rules over three years. The average again includes years with no purchases.

Deficit rule Average buybacks per year Years with any purchase Share of purchases in loss-making years, with / without treasury income
Accumulates (current) $2.74M 42% 14% / 20%
Reset every year $2.96M 51% 21% / 31%
Reset every quarter $3.05M 57% 29% / 38%

A yearly reset adds about $0.2M of buybacks a year, roughly 8%, and makes NEST buy in more years. The price is that a purchase is about one and a half times as likely to land in a year the DAO ends at a loss. In dollar terms the amount bought in such years stays small, about 2–6% of the total in every variant, because those purchases are usually modest. A reset on 1 January 2027 would also simply write off the current deficit.

So a reset does not change the picture much in either direction. It makes buybacks a bit more regular but does not make them larger in any meaningful way, and it weakens the protection the deficit gives. The budget lever moves buybacks by millions, the reset by a couple of hundred thousand. If the DAO wants a reset anyway, it makes the most sense once the threshold already follows the budget, so that a fresh start each year coincides with a freshly approved budget.

These figures come from a new set of price paths starting on 1 October, so they differ slightly from the tables in the report. The script and results are in the repo. lido-nest-analysis/nest_research/followup_budget_reset.py at main · 0xkzmch/lido-nest-analysis · GitHub

Happy to run other budget levels or a different reset date if that helps with the request.

6 Likes

I’m interested in a different question. If the parameters were configured that way from the start, why didn’t any of the delegates conduct research or look into the situation? Why did everyone simply vote mindlessly—just for the sake of it—as happens in 100% of cases? Why did the team itself create a non-functional product and launch it?

* This isn’t a dig at you personally; I’m just trying to understand the logic.

2 Likes

Fair question, and I do not read it as a dig. I think the honest answer is less dramatic than “nobody looked”.

NEST is not broken in the sense of doing something it was not designed to do. It was built to buy only from surplus and to carry any shortfall forward, so that the DAO never buys back with money it has not earned. Right now there is no surplus over the $40M reserve, so it does not buy. That part works as intended.

What was missed, in my view, is how sensitive this setup is to the ETH price and how little room it leaves. With the current modules the reserve is only covered with ETH above roughly $2,668, and for most of the previous year ETH traded well above that, so a fixed $40M looked conservative rather than restrictive. It is much easier to see the problem now, with two months of live data and an on-chain deficit, than it was from a forum proposal.

It is also worth remembering that NEST itself was a long-awaited step. For years the link between Lido’s revenue and LDO was only discussed, and the team did a lot of work to turn it into a working on-chain mechanism, with the allocator, the revenue source, the oracle, the revenue source etc. Getting the first version live is the hard part. I think adjusting its parameters once there is real data is the normal next step.

4 Likes

Thanks for the honest answer.

The thing is, the product was in development for six months, and then another two months were spent realizing that it doesn’t work and is creating a deficit.

Do I understand correctly that for NEST to start buying anything, new funding parameters for 2027 need to be entered first, then the $500k deficit covered, and only then will buybacks begin? It’s a real shame that a year was wasted.

2 Likes

Not quite. NEST has been live since 10 August, so it is two months, not six.

The deficit should not be read as something negative. It is the protection that makes NEST buy only from money the DAO has actually earned, and it does not need to be covered separately, it is paid off automatically once there is a surplus. That can happen if ETH rises well above roughly $2,668, but the DAO cannot control the ETH price. What it can control is its own side, and in the model a $30M threshold with ETH around $2,700 clears the current deficit within one to two months.

3 Likes

Yeah, my mistake—fixed it.TY

3 Likes

The bottom-up approach to reviewing the overall budget is not entirely reasonable. Instead, Lido should set a maximum spending cap based on the protocol’s actual surplus-generating capacity, and then use that cap as the basis for selecting which projects to pursue and which operating expenses are necessary, rather than allowing spending to grow without limits.

The maximum budget cap could be set as a percentage of Lido’s total revenue.

For an established and stable protocol that has been operating for years, annual spending of $30 million is simply too high.

1 Like

cp0x supports tying the NEST threshold to the approved budget and splitting the budget into running costs and new initiatives.

On the spending cap, we agree that spending should start from a limit rather than grow by default. We would just not make that limit impossible to raise. Lido’s revenue moves with the ETH price, and a fixed cap would force cuts to development exactly in the years when revenue is weak and the protocol most needs to invest. A simpler rule is a clear base budget, with anything above it, whether a new initiative or higher running costs, coming as its own proposal that also raises the NEST threshold. That way every increase is visible and its cost in buybacks is clear.

For this to work, the budget needs a breakdown by line items, which @BCV already asked for in the GOOSE-2025 report thread, and each new initiative has to say upfront how it will be judged. When we looked at 58 large spending and incentive decisions at Lido, Aave, Sky and Uniswap, almost all of them named a goal, but only 14 had one that public data could check a year later (How DAOs allocate resources). A metric, a baseline, a target and a review date before the vote would already change that, and an initiative that misses its goal should simply end instead of quietly becoming part of the base.

7 Likes

When launching new product modules, Lido DAO should establish clear rules from the outset. For example, with Lido Lend, a predefined percentage of the revenue generated by the new module should be used to buy back $LDO on the open market and burn it.

This mechanism should be clearly defined when the product is launched, rather than replaced with vague statements such as “we can discuss this once the product becomes profitable.”

Each new module should have an explicit rule specifying what percentage of its revenue will be allocated to buying back and burning $LDO on the open market. After the module has been running for some time, the community can vote to adjust this parameter if the original allocation proves unreasonable.

2 Likes

Fully agree the rule should be there from day one. With NEST we already saw what “we’ll connect it later” looks like, CSM and Earn income still isn’t counted.

I’m less sure about a fixed share of revenue though, and I actually tested it. Here is the current NEST next to a rule that sends 10% of net staking revenue to buybacks every day with no threshold, in a stress test on 10,000 scenarios with expense swings, one-off losses and report delays.

Current NEST 10% of revenue to buybacks
Average buybacks per year $2.26M $3.18M
Buys at least once 50% of scenarios always
Share of purchases in loss-making years 21% 56%
Buybacks run more than $1M ahead of what the DAO earned 10% of scenarios 75% of scenarios

It buys more and buys every time, but more than half of it happens in years the DAO is at a loss, so it’s the treasury paying for buybacks rather than profit. A new module usually loses money for its first year or two, so the effect would be even stronger there. What I’d do instead is plug every new module into NEST from launch. Its revenue counts right away, and once the module starts making money, buybacks grow with it.

The numbers are on the Stage5 sheet of the model: lido-nest-analysis/nest_model.xlsx at main · 0xkzmch/lido-nest-analysis · GitHub

5 Likes

The correct buyback approach should have been like this all along. Please, team, speed up implementation. Don’t do formalism. LDO holders should have been one with the team. Formalism will only cause losses to the treasury and all holders. Holders themselves would also have better trust and motivation to jointly push forward LDO’s future business development. This is also a reasonable plan for a DAO. Everyone should pull together. At the same time, I also believe in the LDO team. Right now is exactly when we should be united.

2 Likes

The news that VanEck has withdrawn its application for a Lido Staked ETH ETF ( Cointelegraph on X: "🚨 TODAY: VanEck has filed to withdraw its Lido Staked Ethereum ETF registration with the SEC, saying it no longer plans to move forward with the fund." / X ) goes to show that even institutional players are backing down when faced with complex mathematics and fees. The market is in turmoil, major players are recalibrating their plans, and for our project, this creates a perfect window of opportunity—one that will close very quickly.

As long as key initiatives remain pending on the forum, we are losing momentum. We need to take action right now:

• My proposal for a financial audit Mandating a 2-Year Financial Audit : Demand for Product R&D and Payroll Transparency : It is critical that we fast-track the approval of an audit. Without a clear understanding of our reserves and vulnerabilities in the current climate, we won’t be able to maneuver with the necessary agility.

• The proposal regarding buybacks NEST: tying the buyback threshold to the approved budget : We need to either approve the buyback mechanism or refine it immediately. We require an aggressive and effective tokenomics strategy right now to protect the project and attract liquidity while the industry giants are stalling.

If we continue to drag our feet on voting and discussions, we’ll simply be wiped out by the next market wave. It’s time to wake up.

2 Likes

Hi,Kuzmich

When will the final proposal and the vote take place?

1 Like

As I see it all together with the 2027 grant request, which is expected end November

1 Like