Safe allows secure management of blockchain assets.
This release fixes incorrect exports in the package.json file and contains no other changes. Please refer to the 1.4.1 release for a complete overview of the changes.
See CHANGELOG.md for a complete list of changes.
The changes have been audited, and the report is linked in the readme.
Information on the bug bounty can be found in the developer portal.
The addresses of deployed instances of this version can be found in the Safe deployments repository
See CHANGELOG.md for a complete list of changes.
The changes have been audited, and the report is linked in the readme.
Information on the bug bounty can be found in the developer portal.
The addresses of deployed instances of this version can be found in the Safe deployments repository
This release is deprecated in favour of 1.4.1 because of an important bug fix related to ERC-4337 compatibility. You're free to use the code, but it will not be supported in Safe's infrastructure
The release is exactly the same as v1.3.0, the only change is that the SignMessageLib contract was audited, moved out of examples, and deployed.
See CHANGELOG.md for a complete list of changes.
The changes have been audited and the report is linked in the readme.
Information on the bug bounty can be found in the developer portal.
The addresses of deployed instances of this version can be found in the Safe deployments repository
See CHANGELOG.md for a complete list of changes.
The changes have been audited and the report is linked in the readme.
Information on the bug bounty can be found in the developer portal.
The addresses of deployed instances of this version can be found in the Safe deployments repository
All changes are collected in https://github.com/gnosis/safe-contracts/milestone/4?closed=1
The changes have been audited by G0 Group and the report has been added to the repository. See G0 Group audit
The new Safe contract have been deployed to Mainnet, Görli, Rinkeby and Kovan and is on the same address on all networks.
send and transfer calls #154All changes are collected in https://github.com/gnosis/safe-contracts/milestone/3
The changes have been audited by G0 Group and the report has been added to the repository. See G0 Group audit
The contracts have been deployed to Mainnet, Görli, Rinkeby and Kovan and are on the same address on all networks. All information can be found in the following files:
All changes are collected in https://github.com/gnosis/safe-contracts/milestone/2
The changes have been audited by G0 Group and the report has been added to the repository. See G0 Group audit
The contracts have been deployed to Mainnet, Görli, Rinkeby and Kovan and are on the same address on all networks. All information can be found in the following files:
Release of the formally verified contracts. These contracts are deployed to all major networks and are available via npm
The addresses of the contracts can be found in the zos files. Currently it is not possible to verify contracts compiled with Solidity 0.5.0 on Etherscan. It is possible to verify the master copy by compiling the contracts using solc 0.5.0+commit.1d4f565a.Emscripten.clang (solc --bin-runtime contracts/GnosisSafe.sol) and comparing the bytecode (this can also be done via https://remix.ethereum.org/). Be aware that the last 34 bytes can differ since these are a hash of meta data generated by Solidity (see https://solidity.readthedocs.io/en/latest/metadata.html).