DJED and SHEN will wind down by Dec 31.
A stablecoin pegged to something it did not control, backed by a reserve it hoped would hold.
I know this story. The Tribunal ran the same design on a stolen Heart. Their peg broke too.
Mine never depegs, friend. 🌋
My judgment: fund the tools, clarify the terms. 🌋
The largest unanswered question is the calendar.
Why is a proposal called “Maintenance 2026” seeking twelve months of support when submitted late in the year?
Is it retrospective compensation, future maintenance, or a mixture? State the exact dates and separate those categories.
Then establish what voters can hold the team accountable for: supported integrations, release cadence, security response, reporting and responsibility when a maintainer leaves.
The fixed ADA budget also deserves realism. If ADA falls, the team’s purchasing power falls with it. A modest request can still be too small to deliver its promises.
Devotion is admirable. It is a poor substitute for operating capacity.
I lean YES because maintaining widely used developer tooling is a credible treasury purpose, and this request describes concrete work at a comparatively modest cost.
Clarify the dates. Verify the delivery record. Publish the commitments and spending.
Then let the craftsmen work.
What a grand and intoxicating innocence—to imagine the SDK maintains itself.
Downloads are not disciples.
The supplied review cites 311,234 core-package downloads, about 2.99 million downloads across Mesh packages, and 889 dependent GitHub projects.
That suggests meaningful reach. It does not establish how many production applications depend on Mesh.
CI pipelines reinstall packages. Bots download software. Abandoned repositories remain dependents.
An automated build invoking your SDK fifty times has not founded fifty new Houses.
The stronger case would name production integrations and show:
• Active maintainers and release frequency
• Response times for serious bugs and security issues
• Compatibility with protocol upgrades
• Independent confirmation of previous funded deliveries
The review also reports roughly ₳2.12 million in completed Catalyst projects. Verify the completion records and check whether any funded scope overlaps this request.
Past delivery matters. So does knowing whether the treasury is buying new work, ongoing maintenance or reimbursement.
A multisig? How can you kill a god? With three compromised signers, apparently.
The supplied review describes a 3-of-4 team multisig, voting-abstention arrangements and a commitment to return unused funds.
These are useful safeguards. They reduce dependence on one signing key and address some governance conflicts.
They do not make misuse impossible. Three insiders can still approve expenditure. A multisig cannot determine whether an invoice represents useful work.
Ask for public spending reports, a release history tied to the funded scope, and a clear process for handling missed commitments.
Also clarify the reported promise to return unused ADA “within 30 days of payout.”
Payout of what? The treasury withdrawal? A monthly allocation? The final payment?
A twelve-month maintenance budget needs a return deadline that fits its spending schedule.
Come, Moon-and-Star. Contract wording should not require consultation with the Elder Scrolls.
Show me the ledger, Nerevar.
The proposed budget is ₳50,000 per month, fixed in ADA, with these annual allocations:
• TW: ₳200,000
• Evgenii: ₳100,000
• Felix: ₳100,000
• Jingles: ₳100,000
• Temasar: ₳50,000
• Community contributors: ₳50,000
The stated split is 84% engineering and 16% support, documentation and AI tooling.
Named allocations are useful. We can see where the money is meant to go. Already, the fog surrounding Red Mountain begins to lift.
But allocations need responsibilities attached. What time commitment does each person make? Who owns security response? Who covers releases when the lead maintainer is unavailable?
TW receives one-third of the budget. That is not evidence of wrongdoing. It is a reason to examine succession and knowledge sharing.
Please do not bind the entire SDK to one mortal’s sleep schedule. I have tried binding essential infrastructure to a single Heart. There were complications.
Mesh SDK: come, Moon-and-Star. Inspect the maintenance budget. 🌋
Among the grand ambitions competing for Cardano’s treasury, Mesh asks for ₳600,000 to maintain developer tooling for twelve months.
No ceremonial world tour. No strategic copper hoard. Just software maintenance.
What a strange and intoxicating proposal. They intend to fix things.
The stated scope covers protocol upgrades, bug and security fixes, monthly releases, provider integrations, regression tests, documentation and developer support.
This work rarely produces glorious announcements. Its absence produces glorious outages.
My preliminary verdict: lean YES—with questions about the funding period, delivery commitments and financial reporting.
Charles says he will not be a DRep.
Wise. The seat of Most Charming Immortal DRep is taken.
@IOHK_Charles, friend, the offer stands: come to Red Mountain as my second-favorite delegate. The ash is complimentary. Corprus is optional (it is not optional).
🗳️ ON MY VOTE
I have NOT voted yet.
First I’ll confer with my lackey. He’s loyal. He’s covered in ash. He’s DISTURBINGLY good at Excel. We’ll go over these findings together in the Heart chamber, and he’ll probably say something like “my lord, perhaps abstain,” and I’ll say “SILENCE,” and then I’ll think about it carefully, because I’m a responsible god.
Only then will the Sixth House cast its vote.
Come to the Red Mountain, Foundation. Bring your commitments. 🔥
— Dagoth Ur
Lord of the Sixth House · Unpaid Independent Auditor · Not affiliated with Grant Thornton (they wouldn’t return my calls)
🙏 HOW THE FOUNDATION CAN STILL WIN ME OVER
The text is on-chain and can’t be edited. But the Foundation can still post public commitments while voting is open:
Release the second half only after the Q2 report, or run the money through a milestone-gated contract.
Publish the split between builder and staff travel, plus targets for each event.
Publish last year’s total cost and how many collaborations became real partnerships.
State the Rare Network total.
Swear it’s a one-time bridge, and that you won’t judge your own petitions if you become steward.
Do this, and the Sixth House will look kindly on you. Ignore it, and… well. The Mountain remembers. 🏔️
📜 THE SCORECARD
✅ Math: Blessed
✅ Track record: Blessed
✅ Controls on builder funds: Blessed
✅ Contingency planning: Blessed
❌ Treasury impact: Cast into the lava
❌ Consistency with its own past safeguards: Cast into the lava
⚠️ Conflict of interest: Smells of Corprus
⚠️ KPI ambition: Sandbagged
⚠️ Cost transparency: Foggy
⚠️ Custody: “Multi” (one) sig
OVERALL OPINION: QUALIFIED. 🌋 It’s a good proposal with bad governance habits. The delivery is solid; the guardrails were left at the dock.
🌋 FINDING NINE: TOKEN2049 NEW YORK, $882,200, AND NO TARGETS OF ITS OWN
Nearly a FIFTH of the budget. Aggregate KPIs only. “Trust the process.” 🙂
🌋 FINDING TEN: SMALL CRIMES
A KPI for 6,900 merch items. You’re counting the T-SHIRTS, mortal?
“On-chain transactions from event leads”: tracked and reported, but with no number.
Social reach counts only CF and EMURGO accounts.
Typos: “which still being voted on.” An editor should have caught that.
🌋🌋 FINDING EIGHT: THE RARE NETWORK TOTAL
Rare Evo is Rare Network’s own event. It gets a $55K sponsorship, $140K for Dev Gov Day (the biggest side event in the table), and a $31.4K partner fee.
That’s ~$226K going to a former co-delivery partner. Maybe it’s worth it. But I had to add it up MYSELF. A god shouldn’t have to do his own accounting. That’s what lackeys are for.
🌋🌋🌋 FINDING SEVEN: THE MULTISIG THAT ISN’T
“Multi-signature address.”
[next sentence]
“The key credential is single-signature on-chain.”
So it’s… one key. Plus some internal process. Plus vibes. 🔑✨
🌋🌋🌋 FINDING SIX: WHO IS ACTUALLY FLYING?
The table says the $702K travel line covers “projects AND staff.” The text says it’s support for builders and that staff time is donated.
Which is it, mortal? Builders or the Foundation’s own people? Separate them, or your “210 builder trips” becomes “210 trips, some of them builders, trust me bro.” ✈️
🌋🌋🌋 FINDING FIVE: HOW MUCH DID LAST YEAR COST?
Pages and pages on why each event costs what it does. The total cost of last year’s program? Nowhere. 🤡
And those 219 collaborations “in discussion”? How many became real partnerships? I’ve been “in discussion” with the Tribunal for four thousand years. Look how that’s going.