{Solidity}
Solidity is evolving rapidly
We aim for a regular (non-breaking) release every month, with approximately one breaking release per year. You can follow the implementation status of new features in the Solidity GitHub project.
Contribute to Solidity
Solidity continues to improve with help from our global community. Check out these ways to get involved and contribute to the Solidity project.
Reporting issues and vulnerabilities
To report an issue, please use the GitHub issues tracker. To report a vulnerability, please check out the instructions in the SECURITY.md.
Translating the documentation
Translations help developers from all corners of the world to be able to read the documentation and learn Solidity.
Fixing and responding to issues
Fixing and responding to issues, especially those tagged as “good first issue”, is a great way to get started for external contributors.
Contributing to language design
We welcome Solidity power users, auditors, security experts and tooling developers to get involved in the Solidity language design process. Join the Solidity forum, where existing properties of the language and proposals for new language features can be discussed.
Stay Updated
Stay always up-to-date by following the Solidity blog.
You can see the upcoming changes for the next breaking release by switching from the default branch (develop) to the breaking branch. You can actively shape Solidity by providing your input and participating in the language design in the Solidity forumand participating in the yearly Solidity developer surveys.
Latest from the blog
Transient Storage Clearing Helper Collision Bug
Posted by Solidity Team on February 18, 2026
On 2026-02-11, a bug in the Solidity code generator was reported by Hexens. The bug affects compiler versions 0.8.28 through 0.8.33 when using the IR pipeline. When a contract clears both a persistent and a transient storage variable of the same type, the compiler will emit the wrong opcode (sstore instead of tstore, or vice versa) for one of these operations, because the generated Yul helper functions share the same name and one overwrites the other. We assign this bug a severity of...
Read moreSolidity 0.8.34 Release Announcement
Posted by Solidity Team on February 18, 2026
Today we are releasing version 0.8.34 of the Solidity Compiler. This is a bugfix release that patches an important bug of high severity affecting clearing of storage and transient storage variables in the IR pipeline. If your code does not use delete on a transient state variable, your contract is not affected. The affected pattern has proven to be very rare in practice - only three deployed contracts were found across all EVM-compatible chains. The respective teams have been notified. Projects that compile...
Read moreAnnual Solidity Developer Survey is Live!
Posted by Jacob Czepluch on February 10, 2026
The annual Solidity Developer Survey is now live, and we need your input! Take 5 minutes to share your experience and help us prioritize language design, performance improvements, and developer experience enhancements for the year ahead. We're already working on frequently requested features like eliminating stack-too-deep errors, performance optimization, and stronger debugging tooling – with delivery targeted for H1 2026. Your feedback will help us refine priorities and identify what matters most. Check out our latest roadmap update: 2026 Argot Roadmap Update 📝 Take...
Read morePlayground
Try Solidity for yourself in this simple compiler. For a more fully featured browser-based IDE, try using Remix.
Compiler result
Compiler version:
(0 bytes)
Deployment costs: gas
Bytecode
Assembly
Solidity Events
Past events
