Introducing Safe v1.5.0: Module Guards + Enhanced Smart Account Features

Safe v1.5.0 includes many new features and DX improvements to make Safe easier and more secure. It introduces Module Guards, a new security mechanism that bridges Safe's existing modules and guard systems. The release also includes more convenient signature collection, improved transaction debugging, and the Extensible Fallback Handler for improved composability and targets ZKsync’s new virtual machine, which allows same-address deployments on ZKsync.

Safe has always been focused on one thing: providing the most secure and flexible smart account infrastructure for the Ethereum ecosystem. Today, we're proud to announce Safe v1.5.0, a release that takes Safe smart accounts to the next level while significantly improving the developer experience.

Module Guards: A New Era of Smart Account Security

The standout feature of Safe v1.5.0 is Module Guards—a security mechanism that bridges Safe's existing modules and guard systems. A module guard sets security rules for every module transaction. Before that, Safe owners had to pay close attention to the modules of their Safes’ Smart Accounts, as modules could circumvent the security rules of Guards. Now, Safe owners can set up a module guard next to the guard and enforce global security rules. This makes extensions from the module ecosystem more secure and more accessible.

Additional Improvements

zkSync Network Support: Safe v1.5.0 now runs natively on zkSync networks, ensuring consistent account addresses across networks and solving the problem where users accidentally sent funds to addresses they couldn't recover on zkSync.  

Enhanced Developer Experience: We now provide complete Solidity interfaces for all Safe contracts and improved owner signature validation functions, eliminating scattered interface definitions and reducing potential security pitfalls for developers. There is also better Error handling from failed executions, making it easier for developers to debug why transactions failed.

Enhanced Developer Experience: Safe now provides improved owner signature validation functions, eliminating scattered interface definitions and reducing potential security pitfalls for developers. There is also better Error handling from failed executions, making it easier for developers to debug why transactions failed.

Extensible Fallback Handler: The Extensible Fallback Handler, originally developed by the CoW Protocol team, is now officially part of the main Safe repository. Previously, Safe accounts were limited to a single fallback handler, creating composability issues. The extensible version allows multiple handlers per function, making Safe accounts more modular and composable.

Modernized Signature Validation: We've deprecated legacy ERC-1271 code that was maintained for backward compatibility, providing a cleaner, more maintainable codebase with improved security posture.

A Security-First Approach

Security remains our top priority, and Safe v1.5.0 has undergone an extensive security review. The release has been thoroughly audited by leading security firms Certora and Ackee, ensuring the highest security standards for our users and developers.

We're also updating our to include the new contracts, maintaining our commitment to security-first development while pushing the boundaries of what's possible with smart accounts.

Get Started Today

Ready to explore Safe v1.5.0? Here's how to get started:

• Developers: Check out the and updated documentation

• Learn More: Read about and

Safe v1.5.0 is available now for deployment on all supported networks.