The decentralized finance (DeFi) ecosystem built upon the Ethereum blockchain continues to experience a relentless wave of activity, as individuals and organizations alike deploy token contracts, inject liquidity into automated pools, and launch complex smart contracts to power diverse business models. While this vibrant growth highlights the rapid evolution and adoption of Web3 technologies, it has simultaneously been accompanied by a persistent surge in security exploits. These vulnerabilities have consistently left DeFi protocols exposed to devastating hacks, flash loan attacks, and malicious scams, threatening user funds and shaking confidence across the broader cryptocurrency industry.
Recent intelligence data from blockchain analytics firm Chainalysis underscores the severity of this issue, revealing that crypto-related hacks surged by an alarming 58.3% from the start of 2022 through July of that same year. The report highlights that a staggering $1.9 billion was drained due to malicious exploits during this specific timeframe alone. Significantly, that catastrophic figure does not even account for the high-profile Nomad bridge hack on August 1, 2022, which resulted in an additional $190 million loss.
While the open-source nature of blockchain development is widely heralded as a core benefit that drives innovation, collaboration, and transparency, it also presents a major downside. Open-source code can be easily studied, analyzed, and scrutinized by cybercriminals and bad actors actively searching for security flaws and logical vulnerabilities to exploit. Although third-party security audits for smart contracts were designed to mitigate these exact challenges, the auditing sector itself has historically lacked unified industry standards, creating a fragmented landscape fraught with complexity, inconsistent evaluation criteria, and varying levels of thoroughness among auditing firms.
An Industry Standard to Ensure Smart Contract Security
In an effort to confront these structural challenges head-on, Chris Cordi, chair of the EthTrust Security Levels Working Group at the Enterprise Ethereum Alliance (EEA), spoke about the evolving industry landscape. Cordi noted that as the Ethereum blockchain ecosystem expands in size and financial importance, there is a parallel, urgent need for a mature, standardized framework capable of rigorously assessing the security posture of smart contracts.
Recognizing this critical gap, Cordi collaborated with several EEA member representatives possessing deep expertise in smart contract auditing and cybersecurity to establish the EthTrust Security Levels Working Group in November 2020. Since its inception, the collective has dedicated its efforts to drafting a comprehensive smart contract specification—effectively creating an industry standard designed to elevate security practices across the board.
Most recently, the working group announced the official publication of the EthTrust Security Levels Specification v1. Chaals Nevile, technical program director at the EEA, explained that this newly released specification explicitly outlines the types of smart contract vulnerabilities that a proper, professional security audit must evaluate as a baseline measure of quality.
According to Nevile, the framework holds broad applicability across the broader blockchain sector. He noted that the specification is relevant to all Ethereum Virtual Machine (EVM)-based smart contract platforms where developers utilize Solidity as their primary coding language. Pointing to a recent analysis conducted by Splunk, Nevile emphasized that Solidity accounts for well over three-quarters of all mainnet contracts. However, he also stressed its utility beyond the public mainnet, noting that private enterprise networks and proprietary projects operating on their own independent chains utilizing the Ethereum technology stack can derive just as much value from the specification to secure their codebases.
Breaking down the technical architecture of the framework, Nevile detailed that the newly introduced specification outlines three distinct tiers of testing that organizations must evaluate when conducting smart contract security audits.
The first tier, known as Level [S], is architected so that in the vast majority of cases where standard features of Solidity are implemented following widely recognized development patterns, the tested code can be formally certified through an automated static analysis tool.
Moving up in rigor, Nevile explained that the Level [M] test mandates a much stricter form of static analysis. This intermediate tier incorporates specific requirements where a human auditor is explicitly expected to intervene, evaluating whether the utilization of a particular code feature is genuinely necessary or whether a project’s claims regarding the internal security properties of its code are actually justified.
Furthermore, the Level [Q] test dives deeper by providing a comprehensive analysis of the underlying business logic that the tested code implements. This phase is designed to ensure that the code not only remains free of known security vulnerabilities but also accurately executes the exact functions and promises it claims to fulfill. Alongside these core tiers, the framework includes an optional category of recommended good practices aimed at further fortifying smart contract architecture.
Elaborating on these supplementary guidelines, Nevile pointed out that utilizing the latest compiler version stands out as a straightforward yet crucial recommendation. While updating compilers is simple in theory, he acknowledged that various practical constraints often prevent contracts from being deployed with the most up-to-date versions. Additional recommended practices highlighted within the framework include formally reporting newly discovered vulnerabilities so they can be swiftly addressed in subsequent updates to the specification, as well as authoring clean, easily readable code.
Altogether, the comprehensive specification encompasses 107 distinct requirements. Nevile noted that roughly 50 of these criteria fall under Level [S], addressing fundamental bugs and vulnerabilities that frequently arise directly from issues within Solidity compilers.
Will an Industry Standard Help Organizations and Developers?
Addressing the practical utility of the initiative, Nevile emphasized that the ultimate goal of the EthTrust Security Levels Specification is to empower independent auditors to transparently demonstrate to their clients that they are operating at a professional level appropriate for the industry. By referencing this established benchmark, auditing firms can readily establish a baseline of credibility.
Providing additional perspective on the broader auditing market, Ronghui Gu, CEO and co-founder of prominent blockchain security firm CertiK, explained that standardized frameworks are vital for ensuring expected operational processes and guidelines are followed. However, Gu issued an important caveat, emphasizing that such specifications should never be misconstrued as a blanket "rubber stamp" indicating that a smart contract is completely immune to exploits.
Gu stressed that the auditing landscape is far from uniform, noting that not all smart contract auditors possess equal capabilities. Effective smart contract auditing requires a deep, nuanced understanding of the specific blockchain ecosystem being targeted, alongside intimate familiarity with the underlying technology stack and programming language in use. Because not all codebases or blockchain networks share the same properties, accumulated industry experience remains paramount for ensuring comprehensive code coverage and identifying critical vulnerabilities.
Consequently, Gu advised that companies seeking security audits for their projects should look well beyond basic certifications claimed by auditors, instead weighing the quality, scale, and organizational reputation of the auditing firm. Viewed through this lens, Gu regards the new EEA specification as an exceptionally strong and necessary starting point for the industry.
From the perspective of those writing the code, these specifications are poised to deliver substantial benefits. Mark Beylin, co-founder of emerging blockchain-based social network Myco, noted that standardized guidelines will prove invaluable by helping smart contract developers cultivate realistic expectations regarding what a comprehensive security audit should entail. Beylin remarked that while the Web3 space currently features scattered and decentralized resources regarding smart contract security, it has historically lacked a definitive rulebook that auditors consistently follow when assessing a project. With this new specification, both security teams and their clients can finally operate from a shared understanding of the security requirements being evaluated.
Echoing this sentiment, Michael Lewellen, a developer and active contributor to the specification project, highlighted that the guidelines serve as a practical checklist against known security issues. Lewellen pointed out that many Solidity developers lack formal, up-to-date education or specialized training regarding the intricate security aspects of the language, even though secure code is universally demanded by the market. Frameworks like the EthTrust specification make navigating secure coding practices significantly more accessible.
At the same time, Lewellen offered constructive feedback on the current documentation, noting that while most requirements are articulated clearly, the underlying rationale for certain rules is not always immediately apparent. While some criteria include direct links to external documentation detailing specific vulnerabilities, others do not. He suggested that developers would benefit greatly from clearer, side-by-side examples illustrating what compliant versus noncompliant code looks like in practice.
The Evolution of Smart Contract Security Standards
Ultimately, the introduction of the security levels specification represents a meaningful step forward for the Ethereum ecosystem, helping to establish structured guidelines for smart contract evaluations. Nevertheless, Nevile cautioned that the most formidable ongoing challenge for the industry remains anticipating novel, unforeseen vectors of attack before they are weaponized by bad actors. He noted that while the specification cannot completely eliminate every security risk, it successfully mandates vital preparatory steps—such as rigorous documentation of contract architecture and internal business logic—that lay the groundwork for a truly thorough security audit.
Looking toward the horizon, Gu anticipates that other blockchain ecosystems will naturally develop parallel standards as the Web3 landscape continues to mature. Already, individual developers within the Ethereum community have begun crafting their own supplementary requirements to guide peers. For instance, Samuel Cardillo, chief technology officer at RTFKT, previously launched a public initiative via a shared spreadsheet to rate smart contracts based on development best practices, helping raise awareness for collectors and outlining crucial development dos and don’ts.
While industry participants agree that these initiatives point in the right direction, Gu emphasized that widespread adoption of any standard inherently takes time. Furthermore, Nevile underscored that cybersecurity is a perpetually moving target rather than a static destination. To keep pace with the rapidly evolving threat landscape, the working group has established a feedback mechanism allowing developers and security professionals to submit questions and insights directly. Incorporating this ongoing feedback alongside broader public industry discussions, the EEA expects to issue updated iterations of the specification, with a new version anticipated within the next six to eighteen months.
