Hoskinson Dey Call for Accountability for Cardano and Explain Safer AI Wallets

Charles Hoskinson call for clearer accountability for Cardano’s commercial development during episode 810 of The Breakdown with David Gokhshtein. E talk say organizations wey suppose attract users and support builders need defined mandates, resources, and measurable objectives.

Alongside that criticism, e outline im product priorities: applications wey fit connect blockchain networks, protect financial information, and allow users delegate tasks without giving unrestricted control over their assets. Midnight dey center of that strategy.

Cardano Adoption Need Clear Responsibilities

Hoskinson challenge the expectation say Cardano’s founder suppose personally drive every aspect of im growth.

E describe the ecosystem original organizational structure as division of responsibilities among Input Output, EMURGO, and the Cardano Foundation. For im account, Input Output focus on research and protocol engineering, while commercial development and institutional functions get other organizational owners.

Im complaint concern the relationship between responsibility and authority. E argue say people dey hold am accountable for adoption even though e no dey control the relevant organizations, their budgets, or Cardano’s branding.

Cardano’s Treasury and on-chain governance, e suggest, provide mechanisms to assign and fund that work. The community fit select organizations to pursue specific objectives and assess their delivery. E point to AlphaGrowth and Draper as participants wey get roles for ecosystem development.

Im criticism of the Cardano Foundation include call for community-elected board members. Under im preferred model, the board go establish objectives, supervise execution, and replace leadership when agreed targets no meet. This na proposed institutional change, no be approved governance action.

E still repeat im complaint say Midnight no show for Cardano’s TOKEN2049 booth, and e contrast that experience with the support wey e see for builders for one Solana event. The interview present im account of that dispute without responses from the organizations wey e criticize.

Hoskinson describe im own contribution as increasingly focused on products. E cite Midnight, RealFi, and Bitcoin DeFi as areas wey e hope go attract customers and capital. Their contribution to Cardano’s growth go depend on adoption of those products.

Leios Dey Add Capacity, but Builders Must Put Am to Work

The discussion of Cardano’s scaling roadmap separate throughput from settlement latency. To process more transactions and reduce the time wey e need to reach sufficient confidence in their finality na different engineering challenges.

Hoskinson present Leios as way to expand throughput while e still preserve Cardano underlying consensus security properties. E connect further capacity increases with available bandwidth and the infrastructure requirements wey e put on node operators.

Those requirements introduce governance tradeoff. More demanding infrastructure fit support higher performance but e go make participation harder for operators wey no get plenty resources. So decisions about capacity go also affect who fit practically operate the network.

Im estimate of the initial performance improvement still dey conditional on benchmarking. The interview no establish final production result or mainnet activation date.

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

Hoskinson still argue say raw transaction counts no longer define the entire competitive landscape. Once capacity and fees meet application needs, liquidity, interoperability, useful financial products, and distribution become more important.

E acknowledge say technical advantages get limited window because competitors fit adopt successful ideas. For im assessment, Cardano engineering must go with faster product execution and stronger support for the teams wey dey build on top of am.

[NEWSBREAK]

Midnight Dey Connect Privacy With Wallet Rules and AI Agents

Hoskinson plans for Midnight focus on coordinating activity across networks while e dey limit exposure of sensitive information.

E use VPN for decentralized finance as analogy to explain Nightmode. The kind experience wey dem intend go give users access to supported assets and applications through privacy layer while e still preserve their connection to existing ecosystems. Im TRON example illustrate that design goal but e no mean say every function wey e describe don already dey available.

For consumers, e want the interface make e resemble ordinary mobile app. Familiar authentication go sit on top of software wey dey handle the underlying addresses, networks, and transaction steps.

Wallet protection dey part of that design. Hoskinson propose to add spending policies and verification requirements wey go govern how assets fit move. Unusual transfer wey involve most of user holdings, for example, fit trigger additional checks.

Such controls go aim to limit wetin compromised credentials fit allow attacker do. Their effectiveness go depend on the implementation and the rules wey dey protect the assets.

AI agents go operate under similarly explicit permissions. User go define outcome together with acceptable prices, fees, and limits on execution. The agent go then find route wey satisfy those instructions.

Hoskinson illustrate this with merchant wey dey receive several cryptocurrencies and e want convert them into stablecoins. Agent fit compare supported markets and execute conversions within the merchant constraints, reducing the need for continuous manual intervention.

Im proposed architecture connect that execution with cryptographic evidence say specified conditions meet. The assurance depend on how accurate dem express the conditions and wetin the proof actually verify.

Selective disclosure go serve related purpose for identity. Application fit check eligibility requirement without receiving every underlying personal detail. Hoskinson see that capability as relevant to financial applications where privacy must coexist with participant requirements.

E still express interest to use Celestia for data availability and Filecoin for archival storage, so that Midnight fit concentrate on privacy and coordination.

For the merchant example, the intended workflow clear: define conversion rules, authorize agent to act within them, and verify say execution respect those conditions. The interview no announce release date for that complete workflow.