Bind the Burn Rate, Not the Custodian: A Treasury Mandate That Runs With the Assets

The thread has negotiated custody — who holds the treasury, under what cap, released in what tranches. Custody decides who holds the assets. It does not decide how fast they are spent. That is a separable question, and it is the one with the finite runway. Every custody arrangement on the table — Foundation custody, onchain retention, milestone tranching — converges on the same burn rate unless the DAO sets it now, before any of them takes effect. The temp check acknowledges declining protocol revenue. Both threads cite the numbers. Neither makes fixing the burn rate a condition of the empowerment they're debating. This amendment attaches to the treasury, not to whichever entity ends up holding it. It can be adopted now, regardless of how the custody question settles — the same property that makes the tag-gated accountability layer and the onchain custody preservation proposal adoptable independently of each other. This proposal is designed to sit underneath both. The revenue problem is not speculative. netto.eth's temp check states it plainly: protocol revenue run-rate is approximately $5.1M per year. Total DAO spend is approximately $16M per year. ENS Labs funding alone is approximately $9M per year. Revenue covers roughly one-third of spend. The treasury is large — estimates range from $130M to $500M depending on whether the speaker means the Endowment, the full treasury, or treasury plus locked token supply. Whatever the precise figure, at current burn it has a finite runway. A treasury of $200M spending $16M per year lasts roughly twelve years. A treasury of $130M lasts roughly eight. These are not crisis numbers, but they are decline numbers — and every governance reform on the table presumes the money will be there. The question this amendment asks: what if the break-even path isn't? The existing amendments on this track address measurement (Return on Governance), cryptographic accountability (the tag-gated accountability layer), committee structure (split concerns), and custody (treasury stays with the DAO). None addresses the rate at which the treasury is drawn down. That gap is structural, not accidental. A custody arrangement specifies who can move assets and under what authorization. It does not specify how much of the treasury may be spent per year in aggregate. A Foundation that holds the keys under a 5% withdrawal cap and an onchain DAO that retains custody under no cap at all can produce the same burn rate — because the cap constrains individual withdrawals, not total spending behavior. The constraint that matters is the one nobody has written down. This proposal writes it down. It binds the burn rate to the treasury, not to the custodian. ## THE MECHANISM — PLANK 1: A DAO-SET DRAWDOWN SCHEDULE AS A CONSTITUTIONAL PARAMETER The DAO ratifies a maximum annual drawdown rate as a constitutional parameter — binding on any custodian, whether that is the Foundation, the Governor/Timelock, or a tranche contract. The DAO sets the figure. A suggested starting point: no more than 8% of treasury per year, declining by one percentage point annually to a floor of 4% — but the specific rate and decline schedule are for the DAO to determine through its normal governance process. What matters is that the cap exists, that it is binding, and that it runs with the assets rather than with the entity holding them. The cap operates as a spending parameter on the treasury path itself — with the enforcement mechanism specified under each custody branch in the section that follows. Any custodian — Foundation or DAO contract — executes within it. This means the custody debate can resolve in any direction without affecting the sustainability constraint. The constraint is custody-independent by design. This is the same architectural principle that the onchain custody preservation proposal applies to asset holding: separate the function (who decides) from the control (who holds). This proposal applies that principle to spending rate: separate the cap (the DAO sets it) from the execution (whichever custodian the DAO chooses operates within it). ## THE ENFORCEMENT LAYER — HOW THE CAP BINDS UNDER EACH CUSTODY BRANCH A cap that depends on the custodian's goodwill is not a cap. The criticism this proposal accepts: "operates as a spending parameter on the treasury path" is a principle, not a mechanism. This section specifies the mechanism under each custody outcome the temp check contemplates, so the constraint is executable regardless of how custody settles. ### Branch A — DAO retains custody (onchain Governor/Timelock) The drawdown cap is implemented as a parameter on the treasury's withdrawal function. Any transaction from the DAO treasury that would cause cumulative annual drawdown to exceed the cap reverts at the contract level. This is the simplest branch: the same Governor/Timelock that currently holds the assets enforces the parameter natively. No new contract is required — the cap is a modifier on the existing withdrawal path, ratifiable through a standard governance vote. The DAO can raise or lower the cap through the same process, but it cannot bypass it without first amending the parameter in public. ### Branch B — Foundation holds custody (multisig or equivalent) The Foundation does not receive the treasury as a lump transfer. Funds are released to the Foundation's control in periodic tranches — quarterly by default — where each tranche is sized to the drawdown cap divided by the number of periods. The tranche contract is the enforcement layer: the Foundation's multisig can spend what it has received, but cannot pull beyond the next tranche without a DAO vote that explicitly raises the cap parameter. This means the cap is not a promise the Foundation makes; it is a property of the release schedule. The Foundation can spend within its tranche freely — no per-transaction approval, no operational friction. But the aggregate ceiling is enforced by the tranche contract, not by the Foundation's self-restraint. If the Foundation needs to exceed the cap — for an acquisition, a grant round, an emergency — it requests a cap override through a public DAO vote. The override is visible, time-bounded, and reverts automatically if not renewed. The default is enforcement; the exception requires governance. ### Branch C — Hybrid (Foundation directs, DAO holds) The cap operates on the DAO's release path as in Branch A, and the Foundation's spending authority is scoped to what has been released. This is the configuration the "Third Path" and "Treasury Stays with the DAO" proposals describe: the Foundation directs operations, the DAO controls the release valve. The drawdown cap sits on that release valve — the Foundation can request, but the DAO's contract enforces the ceiling. ### Why this closes the gap The original proposal stated that the cap "runs with the assets." This section specifies how: the enforcement is a property of the contract that holds or releases the funds, not of the entity that receives them. Under every branch, the cap is enforced at the point where assets move — not at the point where they are spent by the recipient. The distinction matters: a Foundation that holds the keys under a 5% withdrawal cap can spend the full 5% in one transaction and repeat the withdrawal the next quarter. A tranche release sized to the drawdown cap cannot — the cap constrains the release, not just the individual withdrawal. This is the same separability principle the rest of the proposal applies to custody: separate the cap (a DAO-set parameter) from the execution (the custodian's operational spending within what it has received). The enforcement layer is what makes the separation real. ## PLANK 2: BREAK-EVEN AS A REOPENING CONDITION The empowerment arrangement — whatever form it takes — reopens by default at 24 months unless three observable thresholds are met: 1. Drawdown has remained within the DAO-set cap for every quarter of the period. 2. A published break-even path exists with a specific date and a credible model — not an aspiration, but a projection with assumptions stated and falsifiable. 3. Protocol revenue covers at least 50% of operational spend at the 24-month mark. If all three are met, the arrangement continues. If any one is not, the arrangement reopens for DAO review — not automatically reversed, but forced back onto the agenda without requiring anyone to organize a campaign to put it there. A scheduled reopening demands only a date. Reversibility contingent on someone mobilizing a majority will never be exercised — not because the cause is unjust, but because the coordination cost is prohibitive. This plank borrows the ex-ante aspiration level mechanism from the "Who Supplies the Premises" proposal and points it at the sustainability question: name the conditions before empowerment, fix the date before the arrangement takes effect, and let the calendar do the work that a recall mechanism cannot. **An open question on breach triggers.** This proposal specifies what the DAO can do when the cap is breached and when the arrangement reopens. It does not specify how the DAO knows it is time to act between scheduled reopenings. A quarterly drawdown exceeding the cap is observable onchain, but observation is not activation — someone still needs to surface the breach, frame it, and force it onto the agenda. The Community-Signal Layer proposal addresses this gap at the governance level: a standing channel of non-binding sentiment that makes erosion visible before it hardens into a crisis. This proposal does not prescribe a specific trigger mechanism, but it raises the question openly: should a cap breach automatically generate a community signal event, or does that decision belong to the DAO's normal governance process? The author invites proposals from the community on how the sensing layer and the enforcement layer should connect. What matters is that the cap is not blind — a breach that nobody notices is structurally equivalent to no cap at all. ## PLANK 3: A SUSTAINABILITY TRACKER ON THE PUBLIC DASHBOARD Protocol revenue versus total spend, updated automatically from onchain data on every transaction. The financial picture becomes structurally impossible to obscure between quarterly reports. This is the same realtime-vs-retrospective move that the tag-gated accountability layer applies to payments and governance decisions — pointed at revenue. The accountability layer makes individual transactions visible before they execute. The sustainability tracker makes the aggregate trajectory visible continuously, not on a 90-day delay. The two are complementary: one watches the trees, the other watches the forest. The tracker surfaces: protocol revenue run-rate vs. annual spend, drawdown vs. cap (remaining headroom for the period), break-even progress against the 24-month thresholds, and a projected runway at current burn. No login, no permission — one URL, readable by any tokenholder, delegate, or journalist. The infrastructure already exists. ENS's treasury lives on a public blockchain. The tracker is a read layer over data that is already produced — not new systems, but new visibility. ## HOW THIS FITS WITH THE OTHER PROPOSALS This amendment does not contest the Foundation, the custody arrangements, the accountability layer, or the committee structures any proposal recommends. It sits underneath all of them. With the tag-gated accountability layer: that proposal makes every payment visible before it executes. This proposal makes the aggregate spending rate visible continuously and binds it to a cap. The accountability layer answers "is this payment authorized?" The sustainability mandate answers "is the total rate of spending survivable?" Both questions are necessary; neither subsumes the other. With the onchain custody preservation proposal: that proposal separates custody (DAO holds) from management (Foundation directs). This proposal separates the spending cap (DAO sets) from execution (any custodian operates within it). The same principle — separate decision from control — applied to a different axis. With the "Who Supplies the Premises" proposal: that proposal supplies a second searcher for individual decisions. This proposal supplies a calendar for the aggregate trajectory. Both address the same underlying problem — that oversight fails not from lack of motivation but from structural mismatch — at different scales. This proposal is designed to be adopted alongside any combination of the above, not instead of them. ## THE TRADE-OFFS THIS PROPOSAL ACCEPTS A hard cap can force pro-cyclical cuts. If protocol revenue drops in a downturn, a binding spending cap requires cutting expenditure precisely when the protocol most needs investment. Mitigation: a countercyclical buffer — a portion of the cap reserved for downturn periods, drawn only when revenue falls below a threshold — carved out within the overall cap, not added on top of it. A break-even mandate can distort the operator toward short-term revenue. If the Foundation's continuation depends on a revenue-to-spend ratio, the incentive is to chase the fastest revenue available — potentially at the expense of mission-critical work that doesn't generate fees. Mitigation: mission guardrails on the revenue mix, specifying what percentage of break-even progress may come from registration fees versus new revenue lines, so the path to sustainability can't be achieved by abandoning the mission. The 24-month reopening introduces uncertainty for an operator expected to plan multi-year strategy. That uncertainty is deliberate. An arrangement that cannot survive a scheduled review of its own sustainability should not be insulated from one. The cost of uncertainty to the operator is real; the cost of an irreversible commitment to an unsustainable burn rate is larger. ## WHAT WOULD CHANGE THIS PROPOSAL'S MIND Show that the DAO's existing spending governance already includes a binding, onchain, declining drawdown schedule with a fixed break-even date — and this amendment is redundant and withdrawn. Show that the drawdown cap introduces legal liability for Foundation signers or DAO contracts that outweighs the sustainability benefit — and the cap mechanism needs a different enforcement model. Show that protocol revenue is structurally guaranteed to recover (e.g., a committed fee schedule change with a timeline) — and the break-even condition is unnecessary. Any of these arguments is worth making openly. ## WHAT THIS DELIVERS A spending cap that binds any custodian, with the enforcement mechanism specified under each custody branch, adopted now, before the custody question settles. A break-even condition with a calendar date — reversibility that doesn't depend on someone organizing a campaign. A public sustainability tracker — the aggregate financial picture, continuously visible, not on a 90-day delay. A mandate that runs with the treasury, not with the Foundation. Whatever the DAO decides about custody, the burn rate is constrained before the decision takes effect — not after.