This site is being rebuilt and some pages are out of date. For current details, write to [email protected]. This notice goes away when the rebuild is done.

No analytics unless you allow it, no tracking. This site keeps in your browser the language you pick, the theme, its colour, which site you chose, the currency on the pricing page and that you closed this notice; signing in adds session cookies. The legal page has the details.

Sign in

Radar · Solidity · Archive · Week 51 · Dec 15 – 21, 2025

Solidity 0.8.32/0.8.33 Release Announcement

Worth knowingcompiler

What changed
0.8.32 is a bugfix release that patches an important bug of low severity. It also resolves an issue that was hampering the use of modules as namespaces for events and errors. 0.8.33 contains a hotfix for a backwards-incompatible…
Production impact
The source does not say.
Try it
Update your build scripts to point to the new compiler versions and verify that module‑based event and error names compile without errors.
Source
soliditylang.org/blog/2025/12/18/solidity-0.8.32-0.8.33-release-announcement

Understand it, then run it

Solidity 0.8.32 fixed a hidden bug that could cause array writes to miss the last slot of storage. The compiler now correctly clears and copies arrays that touch the end of storage, so contracts that use large dynamic types or inline assembly no longer risk losing data. It also fixed an internal error that happened when you tried to emit an event or revert with an error that was defined inside a module and accessed with the M. syntax. That syntax now works as expected. Modules are a way to group functions, events, and errors together, similar to libraries but with better namespace support. With these fixes you can safely use modules to organize your events and errors without the compiler crashing.

Written by gpt-oss-20b from the linked source · claims checked against the sources · archive, not individually reviewed