How to upgrade your Safe to contract version 1.5.0

Last updated: September 22, 2026

Every Safe runs on a version of the Safe smart contracts. Version 1.5.0 is the current version. Safes on 1.3.0 or 1.4.1 can upgrade in one transaction from Settings. New Safes are created on 1.5.0 where it is available.

Upgrading is optional. Safe recommends it.

What changes

Failed transactions return the underlying error instead of a generic revert, so a failure tells you what went wrong. Signature validation moves to the current ERC-1271 standard. Safes that run modules get a Module Guard, which checks every module transaction against the same rules as your other transactions.

The full change list is in Introducing Safe v1.5.0.

What stays the same

Your Safe address, owners, threshold, guards, and modules all carry over. Your assets are not moved. Connected dApps continue to work.

Check your owners before you upgrade

Go to Settings, then Owners.

If every owner is a wallet address, another Safe, or both, upgrade as normal. This covers most Safes.

If one of your owners is another kind of smart contract, check with its provider first. Version 1.5.0 validates contract signatures more strictly. The owner contract must implement isValidSignature(bytes32, bytes) and return the ERC-1271 value in the exact format the standard defines. Some contracts return a response that earlier Safe versions accepted and 1.5.0 does not.

Do not upgrade until you have that confirmation. If that owner is needed to reach your threshold and it cannot produce a valid signature, your Safe cannot execute transactions.

Upgrade your Safe

  1. Open your Safe in Safe{Wallet}.

  2. Go to Settings, then Contract version. Your current version is shown there, with the upgrade if one is available.

  3. Select Update and review the transaction.

  4. Collect the signatures your threshold requires.

  5. Execute the transaction.

Your Safe runs 1.5.0 once the transaction is confirmed onchain.

If you have the same Safe address on several networks, upgrade each one separately.

Frequently asked questions

Do I have to upgrade?

No. Your Safe keeps working on its current version. Features Safe builds next will require 1.5.0.

Does my Safe address change?

No. Your address, owners, and threshold are unchanged.

What does the upgrade cost?

The upgrade is a transaction, so it costs gas like any other transaction on your network.

Why do I not see the upgrade option?

Either your Safe already runs 1.5.0, or 1.5.0 is not yet available on your network. Version 1.5.0 is rolling out network by network. Where it is not deployed, Safe{Wallet} keeps using 1.4.1 and everything works as before.

Can I go back to an older version?

Safe{Wallet} does not offer a downgrade.

Will my modules and guards still work?

Yes. Both carry over. Module transactions are additionally checked by the Module Guard.

Will my connected dApps break?

The contract interface has not changed, so dApps continue to work. A dApp that has hardcoded Safe contract addresses may not recognize a 1.5.0 Safe. Contact that dApp's team if you see this.

One of my owners is another Safe. Is it affected?

No. Owner Safes keep signing as they do today, including owner Safes on 1.3.0 and 1.4.1.