Midgard Warns AI Threats Could Test Cardano’s Security Advantage

Artificial intelligence is creating new security challenges for blockchain networks, and Midgard Labs wants Cardano’s smart contract infrastructure prepared for the risks ahead.

During an X Space discussion titled Decentralizing Cardano’s Core Development, Phil from Midgard Labs warned that increasingly sophisticated attacks could reshape the industry’s competitive landscape. His remarks came as the organization outlined its priorities for taking responsibility for Plutus, Cardano’s smart contract execution system.

Phil identified two closely connected objectives: strengthening security against AI-assisted exploits and making Plutus more responsive to the developers building applications on Cardano.

AI Security Threats Could Challenge Blockchain Networks

Phil believes the next two years could be particularly difficult for blockchain ecosystems, especially those lacking sufficient resources to maintain and secure their infrastructure.

He described the period ahead as potentially decisive for the industry: “I strongly believe that sort of the next two years is do or die for blockchains.”

His warning centers on the increasing capabilities of artificial intelligence to identify potential software weaknesses. Automated code analysis and advanced testing techniques can help legitimate security researchers detect vulnerabilities, but similar capabilities may also be used by attackers.

Smart contracts present a particularly sensitive target because they execute financial operations involving lending, collateral, liquidity, and trading. Vulnerabilities in their implementation can expose users to substantial losses.

Phil expects AI-assisted attacks to place greater pressure on the security assumptions underlying decentralized applications. However, his comments did not identify a newly discovered vulnerability in Cardano or establish that AI has already compromised Plutus.

Why Cardano’s Security-First Development Could Matter More

Cardano has invested heavily in academic research, formal specifications, and carefully controlled software development. According to Phil, those decisions have sometimes required sacrificing faster feature delivery in favor of stronger security assurances.

He argues that the market has historically placed greater value on rapid innovation and application availability than on the potential benefits of Cardano’s engineering approach.

To illustrate the challenge, Phil referenced established DeFi applications such as Aave. Users who have relied on a protocol for years without personally experiencing a serious incident may find claims about another blockchain’s superior security difficult to evaluate.

For those users, security can appear abstract until a vulnerability causes financial damage.

Phil believes that perception is changing as established protocols across the industry experience security incidents. In his assessment, increasingly visible risks could make security a more significant consideration for developers, investors, and liquidity providers.

However, Cardano’s research-driven architecture does not make its applications immune to exploits. Smart contract security also depends on implementation quality, external dependencies, access controls, and ongoing maintenance.

Midgard Makes Plutus Security a Development Priority

The transfer of Plutus development to Midgard Labs gives the organization responsibility for one of Cardano’s most important technical components.

Plutus provides the execution environment used to validate smart contracts, including those supporting decentralized exchanges, lending applications, and other financial protocols.

Phil specifically identified AI-assisted red teaming and exploit resistance as priorities for the execution layer.

Red-team testing involves simulating adversarial behavior to identify potential weaknesses before malicious actors exploit them. AI-assisted techniques could expand the range of scenarios examined during such assessments.

Midgard’s objective is to strengthen the underlying execution environment while maintaining the security principles that have shaped Cardano’s development.

The distinction between Plutus and the applications built with it remains important. Improving execution-layer security cannot automatically eliminate vulnerabilities introduced by individual smart contracts or their surrounding infrastructure.

Phil did not announce a dedicated AI security product, release a testing timetable, or present results from new protective mechanisms. His remarks establish a development priority rather than a completed technical upgrade.

Plutus Development Moves Closer to Cardano Applications

Midgard also intends to address a longstanding gap between engineers developing Plutus and the teams using it to build decentralized applications.

Phil explained that these groups have sometimes approached development priorities differently. Core engineers focus on the language and execution system, while application developers encounter practical limitations when implementing products.

Midgard Labs and Anastasia Labs have contributed technical proposals, conducted security reviews, and collaborated directly with Cardano applications. According to Phil, their work has involved projects ranked among the ecosystem’s 20 largest applications by total value locked at various times.

That experience has allowed the teams to collect feedback about development difficulties and missing capabilities.

Previously, Phil often consolidated those requirements into Cardano Improvement Proposals. Under Midgard’s leadership, he wants a more direct communication channel between application developers and the Plutus engineering team.

He also believes core engineers should spend more time building applications themselves, giving them firsthand experience with the limitations developers encounter.

The proposed approach would allow practical requirements to influence the Plutus roadmap more directly while keeping security central to future improvements.

[NEWSBREAK]

Could Security Risks Shift Liquidity Toward Cardano?

Phil’s assessment extends beyond the technical development of Plutus.

He questioned whether the industry’s large number of independent blockchain networks could remain sustainable through an environment of increasingly sophisticated security threats.

Different ecosystems have significantly different development resources, security budgets, and capabilities for responding to incidents. Phil expects those differences to become more consequential as AI-assisted attacks evolve.

In his view, some blockchain networks could lose relevance while users and liquidity providers increasingly favor infrastructure they perceive as safer.

He hopes Cardano could become a destination for that activity.

However, such a migration remains a prediction rather than a confirmed market development. Phil did not provide estimates of potential capital inflows or identify which networks might lose liquidity.

Security is also only one factor influencing capital allocation. Developers and users require functional applications, sufficient liquidity, reliable infrastructure, and access to competitive financial products.

Cardano would therefore need to combine its security-focused engineering with applications capable of meeting those requirements.

What Comes Next for Plutus

Midgard’s strategy brings together two development priorities: making Cardano’s smart contract execution layer more competitive and strengthening its resistance to emerging security threats.

Phil wants Plutus to better address the needs of application developers while preserving the engineering practices that have historically shaped Cardano.

The team intends to establish more direct communication with decentralized application builders, incorporate practical developer feedback into its proposed roadmap, and prioritize research into AI-assisted attacks targeting the execution layer.

Specific release dates for additional AI-related protections have not been announced.

The immediate organizational change is Midgard’s plan to open communication between application developers and Plutus engineers, allowing teams to raise technical limitations and request features directly.

That structure will give the engineers responsible for Plutus a closer connection to the applications they support, while placing AI-related security concerns among the priorities shaping the system’s future development.