Core Solidity Project Status Update: Prototype Evolution, Community Feedback, and Upcoming Milestones

The development team behind Core Solidity has released a comprehensive status update detailing the evolution of the new frontend for the solc compiler as of early October 2026. Designed to introduce modern language features—such as algebraic data types, pattern matching, generics, traits, and compile-time evaluation—Core Solidity represents a significant structural shift for the Ethereum ecosystem’s most prominent smart contract language. By relocating much of the compiler’s built-in logic into a self-hosted standard library, the project aims to modernize development practices while maintaining backwards compatibility with the underlying infrastructure of Classic Solidity.

Misconceptions surrounding the project have persisted since its initial introduction, with several industry members incorrectly assuming that Core Solidity completely replaces the entire existing compilation pipeline. Project maintainers have reiterated that Core Solidity functions strictly as a new frontend. The backend remains entirely intact; Core Solidity compiles directly down to Yul, handing off the output to the established optimizer and code generator already utilized by solc for Classic Solidity. Prototype testing has continuously verified this architecture, successfully emitting Yul code and routing it through standard compilation pathways for EVM execution.

Current State of the Language and Architectural Refinements

Over the summer, the development team undertook a substantial overhaul of the language’s syntax to align it more closely with expectations familiar to Classic Solidity developers. Consequently, early code snippets published in prior roadmap posts require updates to compile successfully, though the underlying conceptual framework remains consistent. Contracts and functions now feature a recognizable structural layout, with primary differences including postfix typing—where types follow names, such as phase: Phase and amount: uint256—and a strict import requirement that restricts the global scope unless explicitly declared.

A notable introduction in Core Solidity is the algebraic data type, exemplified by enum variants capable of carrying internal data. The standard library, referenced as std, provides essential primitives alongside std.dispatch for handling public function mechanics and std.Generic or std.StorageGeneric for managing state storage. Pattern matching via the match construct enables precise decomposition of these types, ensuring robust type safety by forcing developers to handle all potential variants or explicitly provide a default arm. While the ecosystem continues to mature, current prototypes reflect minor rough edges, such as reliance on plain strings for reverts in the absence of custom errors and specific control-flow syntax requirements that are actively tracked in open repositories.

The prototype compiler hosted within the solcore repository has progressed to the point where it can successfully compile ports of established protocols, including the Ethereum deposit contract, WETH9, and a minimal ERC20 token implementation. These ports are routinely compiled through solc and executed on an Ethereum Virtual Machine as part of continuous integration testing, though event support remains absent in the current build. Developers wishing to explore the language can utilize the web-based playground to inspect generated bytecode, test interactive examples, and analyze modular architectures such as multi-vault compositions and feature-based token extensions. Additionally, formal semantic verification is underway using the Lean 4 proof assistant within a dedicated repository to mathematically underpin the language design.

Missing Features, Open Pull Requests, and Design Choices

While the prototype demonstrates robust foundational capabilities, several critical production-level features remain absent from the main branch of the solcore repository. Development is rapid, with pull requests being opened and merged on a weekly basis, meaning feature lists are subject to continuous evolution. Gas optimization and overall code size reduction have not yet been primary focal points for the prototype, leaving performance comparisons with Classic Solidity for a later phase of development.

Core Solidity introduces several deliberate architectural divergences from its predecessor, most notably the complete removal of traditional inheritance, virtual modifiers, and abstract contracts. Classic-style libraries have similarly been discarded in favor of modern composition models utilizing traits and modules. Reference documentation currently available targets compiler and tool developers, leaving comprehensive guides for general contract developers scheduled for subsequent release phases.

Insights from Community Qualitative Interviews

Since March 2026, the development team has conducted 18 qualitative interviews with protocol architects, security auditors, educators, tool maintainers, wallet engineers, and programming language researchers. These sessions frequently involved participants reviewing Core Solidity code in the live playground, offering vital qualitative data regarding readability and design ergonomics. Algebraic data types and pattern matching received widespread praise, particularly due to the compiler’s strict enforcement of exhaustive pattern matching.

Discussions surrounding inheritance versus composition yielded nuanced perspectives. Auditors and security researchers expressed strong support for the modular approach, noting that explicit function wrapping and localized storage management significantly simplify the process of reviewing a contract’s external attack surface. Conversely, teams reliant on deep inheritance hierarchies requested more comprehensive examples demonstrating how large-scale, real-world protocols can transition to modular composition without directly manipulating raw storage slots. Furthermore, tooling maintainers anticipate minimal friction in adapting parsers to the new syntax tree, though static analysis engines dependent on complex type inference will require updates aligned with the final language specification.

Open questions regarding ABI compatibility and the ultimate scope of the standard library remain under active evaluation. While Core Solidity is engineered to seamlessly call external Classic Solidity contracts using standard ABIs, bidirectional compatibility presents challenges due to the complex data structures found in algebraic data types. The development community remains divided on whether the standard library should remain minimal or expand into a comprehensive framework, prompting ongoing outreach to gather broader stakeholder consensus.

Future Outlook and Community Engagement

As the project looks toward its next milestones, maintainers are actively scoping an initial installable release of the prototype to facilitate broader community experimentation. Upcoming documentation updates, deeper examinations of non-inheritance composition models, and finalized processes for standard library contributions remain primary operational objectives.

The development team continues to engage the global developer community through open-source repositories, weekly public team calls, and upcoming presentations at major industry gatherings. These include scheduled technical talks and hands-on developer workshops at the DeFi Security Summit in Mumbai and Devcon. Stakeholders, auditors, and engineers interested in providing direct feedback or requesting demonstrations are encouraged to reach out via the project’s designated communication channels as development toward a production-ready standard progresses.