This is a joint post from Nomadic Labs, Trilitech and Functori.
TL;DR: AI agents have made finding and exploiting software vulnerabilities faster and cheaper than ever, across the whole software industry, not just blockchains. The same tools have also opened up new ways to check for bugs and defend against attacks, and we have leaned into this heavily. Over 2026, we have used AI to build a continuous audit process for our work on the Tezos L1 protocol and Etherlink, which has found and fixed several issues before they became a problem. But the rapid growth in the use of AI agents also raises the risk that public development branches and discussions may expose security flaws before fixes are deployed. To reduce that risk, as part of a broader strategy to evolve our engineering processes, we are moving our day-to-day development on Tezos L1 and Etherlink from their current upstream location to a private repository starting December 2, 2026. Released source code will remain publicly available under the MIT license, and we are committed to improving the quality of any tools and documentation that we create to help enable anyone to submit protocol proposals through Tezos governance.
2026 has marked a turning point in how software gets built, for us and the rest of the industry. A few core engineers at Nomadic Labs, Trilitech and Functori had already been experimenting with tools like Claude Code and Codex during 2025. They had seen how transformative they could be with the right approach, and witnessed the rapid progress of the frontier models. Over the Christmas holidays, experimentation spread across our teams and by the time we returned to work in January, AI agents were no longer niche.
Like everyone else, we had to figure out what that shift meant in practice. These tools have changed not only how we write code, but also how we review it, test it, and find bugs in it. One thing became very clear: their impact goes well beyond producing new software, and cybersecurity is the clearest example. The adversarial model has changed dramatically in 2026. LLMs and agentic tools have lowered the expertise required to find new 0-days, with close to no prior knowledge of the system being targeted. The whole software industry is feeling it. Mozilla reported around 20–30 security fixes per month for Firefox throughout 2025, rising to 423 in April 2026. Starting July 2026, Cisco introduced twice-monthly security disclosure windows, seven-day advance notifications, and planned quarterly hardening updates for major network operating systems. Google’s Threat Intelligence Group recently published an article in which they outlined how adversaries are leveraging multi-agent systems and LLM-driven pipelines to automate labor-intensive phases of vulnerability analysis, chaining capabilities together to reduce the window between patch disclosure and weaponized exploitation. Similar examples keep piling up and there is even a term for describing this turbulent era: the Vulnpocalypse.
The Tezos ecosystem is no exception. Over the course of 2026:
-
Six security upgrades were proposed and voted on by bakers on the Tezos L1 blockchain to address an ever-growing number of vulnerabilities. Most of these issues were threats to the liveness of the chain, but a few of them could have also put user funds at risk.
-
We shipped four releases of the Octez node to address flaws that put the health of the Tezos L1 network at risk.
As a consequence, we have had to invest significantly more engineering effort in addressing known (often still undisclosed) issues and proactively looking for new ones, to protect the chains and user assets. This shift in engineering focus is real, and it is here to stay. The Tezos bug bounty program, administered by the Tezos Foundation remains a valued source of community input on critical bugs. Yet models keep getting better. Safeguards implemented by frontier labs may not prevent every misuse. And new code keeps being written, bringing with it the possibility of new, increasingly subtle bugs with unexpected impact.
As security work grows, our engineers already spend more of their time working in private, preparing fixes that cannot safely be disclosed before they are deployed. The August 2026 Cosmos EVM incident illustrates why coordinating publication with deployment matters: according to Cosmos Labs’ post-mortem, a public pull request described the vulnerability and its exploitation path less than twelve hours before the first known attack. Six networks were ultimately exploited, even though patched releases were already available.
In addition, routine development can reveal sensitive information: a public branch fixing a seemingly harmless bug, or a discussion about the security of a future feature, can give an attacker a hint on a flaw in software already running on the network. Today, separating public development from private security work relies on every engineer recognising those implications before sharing a change or asking a question.
That is why we have decided to move day-to-day development to a private git repository starting December 2, 2026. Concretely, this means core engineers at TriliTech, Nomadic Labs and Functori working on Tezos L1 and Etherlink will push, propose and discuss their changes in a private Gitlab repository. We will set up automated mirroring of the master branch, meaning that our changes will be made available as soon as they are approved and merged. This change will give us more control over when sensitive changes become public. The software we develop will remain open source under the MIT license. We are committed to improving our documentation and tooling so that anyone can participate fully in Tezos ecosystem governance, including reviewing our changes and submitting protocol proposals. We also continue to welcome external contributions through the public monorepo. Any security vulnerabilities discovered by the broader technical community should also continue to be submitted via the Tezos Foundation’s established bug bounty process.
For almost a decade, the Tezos ecosystem has adapted to meet new realities. Security has been at the core of its design from the start, and systems built to last must be able to respond to threats their designers could not have anticipated. That now applies to how we develop it, too. The tools reshaping software security are not going away, and neither is our commitment to openness in what we ship. The Tezos L1 network and Etherlink are open source projects governed by the community. This change is about timing, not openness: it lets us fix problems before they are exposed, while ensuring these networks remain open source, auditable and governed by the community. Adaptability is a security quality, and it is one that has always characterised the Tezos protocol and its ecosystem. For our part, we will keep sharing what we learn as the industry adapts, and we welcome feedback from bakers, builders and contributors along the way.