The Validator Treasury
Turn 13 ETH into three Ethereum validators. Yield buys back CULT. Forever.
The standard CULT proposal spends treasury ETH to acquire an investee's token. Yield comes from the investee performing well and honouring its burn schedule over 12 to 18 months. The capital flows out and, if the project succeeds, value flows back.
This proposal flips that. Instead of buying a token, the treasury deploys 13 ETH into three Rocket Pool megapool validators under the Saturn 1 architecture. The treasury becomes a node operator on Ethereum. Staking yield accrues in perpetuity. That yield auto-converts to CULT — half burned, half distributed to dCULT stakers — on a recurring cadence, with no expiry date.
The 13 ETH never stops working. The vesting schedule isn't 18 months. It's forever.
What Saturn 1 changed
Rocket Pool launched its Saturn 1 upgrade in February 2026, halving the node operator bond from 8 ETH to 4 ETH per validator and introducing megapools that consolidate multiple validators under a single contract. The protocol-wide fee switch now redirects a share of ETH staking rewards to staked RPL.
Pre-Saturn 1, 13 ETH bought you one minipool and an awkward 5 ETH remainder. Today, 13 ETH supports three full validators backing roughly 96 ETH of total validation. Capital efficiency that wasn't possible six months ago.
Three configurations on the table
Each routes the same 13 ETH differently across operator bond and RPL exposure. Organics' recommendation is Config A — but all three deserve public scrutiny.
Why Config A leads
Three validators is the most capital-efficient use of 13 ETH. The 1 ETH RPL stake captures boosted commission without making the proposal about RPL exposure. And the story it tells The Many is clean: "13 ETH becomes three Ethereum validators backing 96 ETH of decentralised liquid staking, generating perpetual yield for CULT burns and dCULT rewards." CULT becomes a contributor to Ethereum's validator decentralisation — not just a yield extractor.
How the burn and distribution plan works
The existing proposal mechanic expects an investee to swap their token into CULT, burning half and distributing half to dCULT holders. This proposal extends that pattern rather than violating it.
The "investee" is a purpose-built contract that custodies the 13 ETH, deploys it into the Rocket Pool megapool, and routes the resulting staking rewards. On a recurring schedule — proposed monthly — accrued ETH yield is swapped for CULT on Uniswap. Of that CULT:
50% → burn wallet (deflationary pressure, in perpetuity)
50% → dCULT rewards (yield for The Many, in perpetuity)
No 18-month cap. No vesting cliff. The instrument is the burn-and-distribution plan, rewritten as a flow rather than a schedule.
Open design questions
Organics is publishing this draft specifically to get these answered in public. Every one of them is genuine — not rhetorical. If you have an answer, push back.
What changes if this passes
It opens a category. Every yield primitive in DeFi — Lido, EigenLayer restaking, Pendle, Ethena — becomes a candidate for the same pattern. The treasury stops looking like a dormant ETH pile and starts looking like a sophisticated yield portfolio designed by The Many.
The Validator Treasury isn't a deal. It's a primitive.
- Who runs the validator?
Validators need 24/7 uptime. Organics running it is a centralisation vector and a slashing liability. Options: partner with an established Rocket Pool node operator, use non-custodial hosting tied to the contract's withdrawal address, or run it transparently with multi-party monitoring. Each has trade-offs. None are obvious.
- What absorbs slashing risk?
Rocket Pool's design puts the operator bond at risk before rETH stakers — which is exactly correct here because the treasury is the operator. But the proposal needs an explicit answer on what happens to the dCULT yield stream during a slashing event, and whether the RPL bond provides meaningful additional buffer.
- How autonomous is the investee contract?
The cleanest design has zero human touchpoints after deployment — yield auto-swaps on schedule, no admin keys, no upgrade path. But that means no exit if Rocket Pool itself ever has an issue. The tension between immutability and prudent escape valves is the same one CULT itself faces. We should resolve it the same way: in favour of immutability.
- What's the swap mechanism for yield?
ETH → CULT swaps run through Uniswap V2 like everything else. But large monthly buys could move the price meaningfully. TWAP-based execution? Smaller, more frequent swaps? Direct routing to avoid sandwich attacks? This deserves an MEV-aware design.
- When does a solo validator become viable?
32 ETH is the natural next step once Config A has 6–12 months of clean operation. Treat this proposal as the credibility unlock for a follow-on solo-validator proposal, not a competing alternative.
Tear it apart in the Telegram. Tag @CULT_Organics on X with concerns. DM your Guardian if you want it championed. If you're a Rocket Pool node operator who'd partner on operations, we want to talk.
v0.4 will incorporate community feedback. Changelog will name contributors.