Community feedback requested: Aiken maintenance and protocol-readiness treasury proposal

[musik-c]

The Aiken maintainers are considering a Cardano treasury proposal for 12 months of direct Aiken maintenance and hard fork/protocol readiness work. Current maintenance capacity is constrained because contributors have full time employer obligations and varying availability, creating concern that Aiken may not have enough dedicated capacity for upcoming hard fork and Plutus readiness work.

Intersect is currently expected to serve as treasury administrator, but administrator details, payee structure, oversight and final budget assumptions still need to be confirmed before any final submission.

The proposal is intended to fund maintenance capacity for Aiken as open-source Cardano developer infrastructure. It is not intended to create a grant program, DAO, allocator or private product roadmap. The only community facing payment mechanism currently contemplated is a small, maintainer-controlled issue-reward reserve for significant, reproducible reports that reduce maintenance burden.

Why this is being considered

Aiken is used by Cardano smart contract developers and needs ongoing maintenance to remain reliable through:

• upcoming protocol and hard fork changes;
• new Plutus builtins;
• script context changes;
• user reported compiler, runtime, formatter, standard library, CLI, LSP and tooling issues;
• performance and optimization work;
• releases, tests, documentation and migration notes.

The concern is continuity: Aiken maintenance should not depend only on spare time or whether contributors remain assigned to Aiken by their employers or sponsors.

Draft scope

The current draft focuses on:

1. Hard fork and protocol readiness
2. Bug fixes and optimization
3. Developer tooling maintenance
4. A small issue-reward reserve for significant, reproducible public issues
5. Public quarterly reporting, milestone evidence and non-duplication controls

Expected public evidence include issues, PRs, tests, fixtures, releases, documentation updates, compatibility notes, quarterly reports and budget/reward accounting.

Questions for the community

We would especially value specific feedback from Aiken users, auditors, educators, tool builders, protocol teams and DReps:

• Are you using Aiken in production, active development, audits, education or internal tooling? If so, what for?
• What Aiken maintenance work would most improve reliability for production users over the next 12 months?
• What upcoming protocol, Plutus or hard-fork readiness items should the proposal explicitly track?
• What bugs, performance issues, documentation gaps, LSP/editor issues or workflow problems create the most friction today?
• What overlap with other funded work should we check before finalizing scope or budget?
• How should an issue-reward reserve be structured so it rewards significant, reproducible reports without creating noise?
• What would make this proposal easier for DReps and community reviewers to evaluate, audit, support or oppose constructively?

Non-duplication

A final proposal should avoid covering any overlap with employer funded work, Intersect work or related tooling proposals.
If work is already funded elsewhere, the affected scope should be narrowed, delayed, reduced, or removed before disbursement.

Current status

This is a draft discussion. No final treasury action is being announced here. The purpose of this thread is to gather feedback before the proposal is finalized.

[rvcas]

We don't need Aiken

https://github.com/orbistry/nash

[kenerik]

"We don't need Aiken" / "Successor to Aiken" that is a strong statement with those stats on the repo, tho its always good with alternatives

[musik-c]

In some regards my job is to be a steward for Aiken. While I dont contribute code, I will contribute to any DevRel, governance or treasury needs.
I always wish you the best in all your endeavors Lucas. I love product competition, it breeds innovation. Cheers.

[kenerik]

My 50 lovelace thoughts, on top of my head this mornign are:

I think Aiken is an important piece of Cardano infrastructure, and I personaly support the goal of ensuring that it remains healthy, maintained and protocol ready.

For me, the strategic importance of Aiken goes beyond simply maintaining one compiler.
Cardano needs a low barrier entry point for smart contract development.
We should not build an ecosystem where becoming a Cardano smart contract developer effectively requires being a hardcore Plutus expert first.

For that reason, I would frame the treasury case less as:

“fund Aiken maintenance”

and more as:

“ensure that Cardano has reliable, accessible and protocol ready smart contract development infrastructure.

This is more easy to understand from non tech community member.
As they know more developers = More sexy products/utilities for Cardano blockchain = More users.

Im also thinking...
The community should have a transparent overview of what is already being funded through employers, sponsors, Intersect, PRAGMA or other sources, and which specific activities would not be covered by those funding streams

There is a gap of the speed of releases / development throug 2025 vs this year 2026.
Could be nice to educate the community of why that is so.

Then there is...
One additional area I would strongly encourage.

We are very good at cooking up new geeky stuff in Cardano. We need to become equally good at getting the word out and making that technology accessible.
We have historically been weaker (read sucks) at communicating that these products exist, explaining why they matter, and making it obvious to a developer how to actually get started using them to the blockchain ecosystem.

This is where I think Aiken has an opportunity beyond pure maintenance.
As contributors to Aiken are true OG's from the cardano space.

In my view "products build with Aiken" should therefore be treated as an explicit success metric alongside technical milestones. A compiler does not create ecosystem value simply because it works.
It creates value when developers can find it, understand it, and successfully use it.

[musik-c]

Your hired! LOL
Seriously I agree with your points. I am not the best at marketing and getting the word out tho. I am however open to ideas and of course assistance. You interested?