Cardano founder Charles Hoskinson said around 28 minutes into his Nov. 7 AMA that he did not control Cardano’s treasury or consensus and could not negotiate on behalf of all ADA holders. His argument that he cannot act as the ecosystem’s CEO puts a practical question back before holders: who answers for the work meant to grow Cardano?
The answer depends on the decision. Delegated representatives, or DReps, approve treasury spending, the Constitutional Committee checks constitutionality, and funded recipients deliver under the terms of their proposals. Named administrators must monitor fund use and ensure deliverables are achieved. Cardano’s treasury guidance explicitly separates approval from reporting on payouts and results.
Who answers after the treasury vote?
Anyone can propose a treasury withdrawal. It needs DRep and Constitutional Committee approval, must comply with the Constitution and must remain within the applicable Net Change Limit, the cap on how much ADA can leave the treasury during a period.
Those roles answer different questions. DReps decide whether to support funding. The committee’s mandate is limited to constitutionality; it must operate transparently and publish its decisions.
The Constitution’s treasury standards require proposals to state their purpose, delivery period, costs and refund circumstances, and disclose whether the prospective recipient received treasury ADA in the previous 24 months.
Funding requests must also allocate ADA for periodic independent audits and oversight metrics, and designate administrators responsible for monitoring spending and ensuring delivery. While an administrator holds withdrawn funds before disbursement, they must remain in separate accounts the community can audit, with the Constitution’s restrictions on delegation.
Inspect two different delivery records
Intersect’s November 6 update reports that AdaStat’s October maintenance milestone was signed off November 2.
The November 3 consensus report maps code and prototype work to funded Initiative 4. The November 6 report keeps it at development, not mainnet release.
Follow the funding decision to the promised work, its administrator and the public delivery record.
The charter describes obligations, not verified compliance across all projects. AdaStat acceptance is attributed to Intersect. Leios remains development work in the November 6 report. Neither example measures ecosystem-wide adoption.
Cardano’s accountability guidance adds a practical benchmark: open milestone reports, published spending, delivery of the proposed work and return of unused funds where applicable. These expectations help holders judge performance. The requirement to fund an audit, however, is distinct from evidence that a particular audit has happened; refund conditions also depend on the approved terms.
A recent example comes from AdaStat, a Cardano explorer. In its Nov. 6 delivery-assurance update, the Cardano organization Intersect reported that AdaStat’s October maintenance milestone was signed off on Nov. 2. According to that account, AdaStat reported security, error-handling, recovery and usability work.
Engineering reports offer another view. The consensus team’s Nov. 3 update maps Leios implementation and prototype work to Treasury Funding Initiative 4, and maintenance to Initiative 17. It links code changes and releases, giving readers concrete outputs to inspect alongside the funded scope.
The deployment boundary matters. The Nov. 6 development report says the latest Leios changes on the main development branch remain development work rather than a mainnet release.
Hoskinson’s influence remains
Hoskinson remains CEO and founder of Input Output Group, according to its leadership page. His AMA presented building applications as his route to bringing people into Cardano. Later, around 2:19 into the broadcast, he distinguished speaking to his audience personally from speaking as Cardano’s CEO.
Delivery responsibility is also spreading across organizations. IO announced Nov. 5 that consensus engineering would move to the firm Serokell and developer experience to AlwaysTrue, with engineers accompanying their work. The moves follow separate schedules through early 2027, with public coordination through Intersect.
Holders also retain a governance response: they can register as DReps, delegate their voting stake to a DRep or change that voting delegation. That gives them a way to act on funding decisions and voting records. Growth still has to emerge from the work those decisions support, and the meaningful test is whether promised outputs become usable products and services.
