Hoskinson Calls for Cardano Accountability and Outlines Safer AI Wallets

Charles Hoskinson called for clearer accountability for Cardano’s commercial development during episode 810 of The Breakdown with David Gokhshtein. He argued that organizations responsible for attracting users and supporting builders should have defined mandates, resources, and measurable objectives.

Alongside that criticism, he outlined his product priorities: applications that connect blockchain networks, protect financial information, and let users delegate tasks without granting unrestricted control over their assets. Midnight sits at the center of that strategy.

Cardano Adoption Needs Clear Responsibilities

Hoskinson challenged the expectation that Cardano’s founder should personally drive every aspect of its growth.

He described the ecosystem’s original organizational structure as a division of responsibilities among Input Output, EMURGO, and the Cardano Foundation. In his account, Input Output concentrated on research and protocol engineering, while commercial development and institutional functions had other organizational owners.

His complaint concerned the relationship between responsibility and authority. He argued that he is held accountable for adoption without controlling the relevant organizations, their budgets, or Cardano’s branding.

Cardano’s Treasury and on-chain governance, he suggested, provide mechanisms for assigning and funding that work. The community can select organizations to pursue specific objectives and assess their delivery. He pointed to AlphaGrowth and Draper as participants with roles in ecosystem development.

His criticism of the Cardano Foundation included a call for community-elected board members. Under his preferred model, the board would establish objectives, supervise execution, and replace leadership when agreed targets are not met. This was a proposed institutional change, rather than an approved governance action.

He also repeated his complaint that Midnight had not been represented at Cardano’s TOKEN2049 booth, contrasting that experience with the support he observed for builders at a Solana event. The interview presented his account of that dispute without responses from the organizations he criticized.

Hoskinson described his own contribution as increasingly focused on products. He cited Midnight, RealFi, and Bitcoin DeFi as areas through which he hopes to attract customers and capital. Their contribution to Cardano’s growth would depend on adoption of those products.

Leios Adds Capacity, but Builders Must Put It to Work

The discussion of Cardano’s scaling roadmap distinguished throughput from settlement latency. Processing more transactions and reducing the time needed to reach sufficient confidence in their finality are separate engineering challenges.

Hoskinson presented Leios as a way to expand throughput while preserving Cardano’s underlying consensus security properties. He connected further capacity increases with available bandwidth and the infrastructure requirements imposed on node operators.

Those requirements introduce a governance tradeoff. More demanding infrastructure can support higher performance while making participation harder for operators with fewer resources. Decisions about capacity therefore also affect who can practically operate the network.

His estimate of the initial performance improvement remained conditional on benchmarking. The interview did not establish a final production result or a mainnet activation date.

Hydra provides a complementary approach for suitable applications. While the base ledger offers shared network capacity, Hydra Heads allow participants to process activity in dedicated off-chain environments. Their performance depends on the workload and configuration.

Hoskinson nevertheless argued that raw transaction counts no longer define the entire competitive landscape. Once capacity and fees meet an application’s needs, liquidity, interoperability, useful financial products, and distribution become more significant.

He acknowledged that technical advantages have a limited window because competitors can adopt successful ideas. In his assessment, Cardano’s engineering must be accompanied by faster product execution and stronger support for the teams building on it.

[NEWSBREAK]

Midnight Connects Privacy With Wallet Rules and AI Agents

Hoskinson’s plans for Midnight focus on coordinating activity across networks while limiting the exposure of sensitive information.

He used the analogy of a VPN for decentralized finance to explain Nightmode. The intended experience would give users access to supported assets and applications through a privacy layer while preserving their connection to existing ecosystems. His TRON example illustrated that design goal without establishing that every described function was already available.

For consumers, he wants the interface to resemble an ordinary mobile app. Familiar authentication would sit above software handling the underlying addresses, networks, and transaction steps.

Wallet protection is part of that design. Hoskinson proposed adding spending policies and verification requirements that govern how assets can move. An unusual transfer involving most of a user’s holdings, for example, could trigger additional checks.

Such controls would aim to limit what compromised credentials allow an attacker to do. Their effectiveness would depend on the implementation and the rules protecting the assets.

AI agents would operate under similarly explicit permissions. A user would define an outcome together with acceptable prices, fees, and limits on execution. The agent would then seek a route that satisfies those instructions.

Hoskinson illustrated this with a merchant receiving several cryptocurrencies and wanting to convert them into stablecoins. An agent could compare supported markets and execute conversions within the merchant’s constraints, reducing the need for continuous manual intervention.

His proposed architecture connects that execution with cryptographic evidence that specified conditions were met. The assurance depends on the conditions being expressed accurately and on what the proof actually verifies.

Selective disclosure would serve a related purpose for identity. An application could check an eligibility requirement without receiving every underlying personal detail. Hoskinson sees that capability as relevant to financial applications where privacy must coexist with participant requirements.

He also expressed interest in using Celestia for data availability and Filecoin for archival storage, allowing Midnight to concentrate on privacy and coordination.

For the merchant example, the intended workflow is concrete: define conversion rules, authorize an agent to act within them, and verify that execution respected those conditions. The interview did not announce a release date for that complete workflow.