After all the drama, who is ready for some excitement? Introducing Bullet!
Bullet is an intention-based account abstraction tool for Cardano. I know that sounds like a word salad so let me just tell you the important details you care about.
The "constrained" workflows (not necessarily ultracode) that companies use to produce working products with models is as valuable as the models themselves. These workflows aren't necessarily hands off no one views the code. They are tight, repeatable units of work.
Mithril needs to be included in the node itself, with an optional configuration you can explicit set to disable participation. There should be no concept of Mithril adoption, no work / effort to onboard SPOs to participate, no work to figure out an economic incentivization mechanism for participation, all of which would be the case if we ship it inside the next node release.
@Cardano_CF
Please reconsider the NO vote on the Plutus proposal.
After reading the rationale, I think several points misunderstand the scope and impact of the work:
The proposed features are strictly additive. Existing languages and tooling can continue operating on the current Plutus version without immediate changes. This is not forced breakage for downstream compilers; a significant amount of engineering effort goes into preserving that compatibility.
Most proposed builtins are performance-oriented. The community has consistently asked for cheaper execution, better script efficiency, and higher-throughput smart contracts. Several of these proposals also originate from community-driven CIP discussions, which reflects clear ecosystem demand for the capabilities these builtins provide.
Plinth is not just “one language’s tooling.” It also serves as a reference implementation for Plutus. Improvements there help clarify semantics, surface edge cases, and provide guidance that other ecosystem tools can rely on.
ZK builtins are not feature bloat. Without them, many ZK applications are either impossible or only feasible in a very limited form on Cardano. If we want Cardano to support serious zero-knowledge cryptographic applications, these builtins are necessary.
Budget transparency and downstream coordination may be worth discussing, but they should not be conflated with the technical value of the proposal itself.
This proposal strengthens the foundations of Plutus and expands what developers can realistically build on Cardano, which I believe is essential if Cardano is going to remain competitive with smart contract environments of other blockchains.
All Dreps, I ask you to vote YES on this proposal!
It might seem like a boring proposal, but the ROI after this is delivered is immediate. The past improvements showed this.
For those who voted NO, please reconsider your vote. Plutus is not done; we can improve so much more.
Call to action, DReps! Please consider voting yes for the IO Plutus proposal. Whether you voted already or not, reading this thread is kindly appreciated 🙇 (and worth it 😉).
In my opinion, this proposal is vital and of high impact/ROI. I'll explain it with examples!
🧵
(1/10)
CIP 42: serialiseData built-in
The need for this built-in came from Hydra, as it needed to hash plutus data on-chain for its fanout, but many projects use it today for weird tricks (@MicroProofs can show you 😉). Credits to both @_KtorZ_ and @ch1bo_ on this!👏 (4/10)
In this day and age, a LLMs worth is not in features or apps it can one shot nor in the plans it can generate. It's in the questions it uses to interview you. Everything else, from the understanding you have to the plan it makes, is downstream of what a LLM asked you.