Cast by adamhurwitz.eth
Over 1 month of @safe v1.5.0 in production and >1.33 years published (Jul 3 2025) Summary • Improved error messages important if transactions break to get them working safely • Module + guards working together is useful for custom security access controls • Like trading specific assets and freezing transfers • Signatures checked more strictly for smart contract based Safe signers with the latest ERC-1271 standard • No difference for externally owned account EOA signers
3 replies
Before upgrading make sure to verify your Safe(s) do not have signers that won't be able to sign transactions post upgrade Compatible • All EOAs: Open the address in Etherscan > EOAs are labeled as "Address {0x...}" • Smart accounts are labeled as "Contract {0x...}" • Safe accounts ≥v1.3.0 • Other smart accounts: Verify it implements "isValidSignature(bytes32, bytes)"
Safe v1.5.0 is included in Safe's up to $1 million bug bounty program
Here's some things I look at for version upgrades farcaster.xyz/adamhurwitz.eth/0xd6c6e0eb
Safe v1.5.0 holding up in production for over a month is a solid sign. Better error messages matter a lot, a confusing failure is how people make costly mistakes. Have you tried the module and guards setup yourself, or are you still on the default config?
)
