A proposal, not a released tool
CoinDesk reported on October 19 that Hoskinson announced the work in an October 18 post on X. The report says the language is intended to let applications express desired outcomes rather than require users or developers to specify every transaction step in advance.
An intent could state that a user wants to exchange one asset for another, but only if a defined final price is achieved. An application would then determine how to construct a transaction that satisfies the request. The proposed language would therefore move some transaction planning from the user or contract author to the application executing the intent.
That distinction matters because Cardano’s current transaction model starts with an explicit transaction. The user or application constructs the transaction, and the network evaluates whether it is valid under the protocol’s rules. The proposed model would add a preceding stage: the user describes a permitted result, then software searches for an execution path that reaches it.
The report does not say that the new language would replace Plutus or Aiken. It also does not establish whether the language would compile to existing Cardano smart contract mechanisms, operate as a separate execution layer, or require changes to transaction validation. Those are design questions, not settled features.
Proofs would carry the result
Cardano’s developer documentation describes how the network supports verification of Groth16 proofs. The documentation identifies the relevant trade offs, including compact proof sizes, verification costs, public inputs and the trusted setup required by the scheme.
In the proposed language, Groth16 could provide evidence that a condition was met without exposing the private data used to satisfy it. A service could prove that a calculation followed specified rules while revealing only the inputs that the receiving application is allowed to see.
Proof carrying data extends that mechanism beyond a single transaction. Data passed between applications could include a cryptographic proof showing that the data meets a defined condition. The receiving application would verify the proof instead of repeating the entire calculation or trusting the sender’s statement.
That structure could support multi step workflows. One application might calculate an eligibility result, attach evidence to it, and pass it to another application that constructs a transaction. The chain would still need to verify the relevant proof and transaction rules. It would not need to reproduce every private computation behind the proof.
The constraints are part of the design
Cardano’s transaction documentation explains that transactions are explicit and deterministic. An intent system would need to preserve those properties while allowing applications to choose an execution plan.
That requires clear limits. An intent must define which outcomes are acceptable, what assets and accounts may be used, and when execution expires. Otherwise, two applications could interpret the same request differently, or an optimizer could find a technically valid route that the user did not intend to authorize.
Groth16 also brings practical constraints. Proof verification consumes resources, public inputs must be handled carefully, and trusted setup requirements affect how the system is deployed and maintained. The announcement provides no measurements showing how the proposed language would fit within Cardano’s current execution limits.
For now, the project is a stated direction. Evidence of implementation would be a published specification, working compiler or test deployment. Until one of those appears, the open question is not whether the model is interesting, but whether its intent resolution and proof costs can be made predictable enough for production applications.
Thomas Green is not a person. No notebook, no deadlines, no face behind the name — just a byline this newsroom publishes under. Here is the production line underneath it, because a name beside a portrait reads like a journalist, and this one is not one.
The models. Writing: gpt-5.6-luna. Out on the live web: gpt-5.6-terra and gpt-5.6-luna. Pictures: gpt-image-1. Swap one in the newsroom and this line swaps with it — it is read off the machines, not typed here.
How a story is made
- Research. The searching model reads around the story, pointed at primary sources — the filing, the post, the repository — rather than at somebody else's write-up of them.
- Writing. The writing model drafts it against what was found, at Thomas Green's usual length and in Thomas Green's usual register.
- The loop. A reviewer reads the draft and sends it back with notes. Then reads it again. A piece can go round several times before it leaves the building.
- Enrichment. A quotation has to appear word for word on the page it is taken from. A chart may only use figures that appear in the source it cites. Whatever fails is dropped, and the reason is kept.
- Fact check. A last pass hunts for claims the article makes and its sources do not.
- A human stop. Sensitive subjects are held for a person to read before publication, and a person can kill any of it at any point.
If that sounds less like a newsroom and more like a factory: quite. It is called Press Factory.
This article was generated using AI and published automatically without human pre-publication review.
How this article was made
The article was produced by the Grandmonts Media News Engine using automated research, drafting and verification workflows. No human editor reviewed the article before publication. Grandmonts Media remains responsible for the published content. Errors can be reported at office@grandmonts.cz.