Submitted by bronze_pickaxe, also found by imare
Safes created outside of the Brahma ecosystem should be able to seamlessly integrate into the Brahma. This Safe should call WalletRegistry.registerWallet to register. After registration,
this safe will be a consoleAccount and should be able to use the same functionality that all the other consoleAccounts have.
However, Safes that have been created using version 1.4.0=< are not fully compatible with Brahma. This is because, in version 1.4.0, IERC165 support has been added to the GuardManager.sol, this is the code added:
This means that every Safe that has been created using Safes contract version 1.40 and up, can only add guards that support the EIP-165 interface, as read from the CHANGELOG.md
Consider the following:
Because the SafeModeratorOverridable.sol does not support the EIP-165 interface:
This means that every Safe created with version 1.4.0 or up, can not implement the guard contract, which is a fundamental part of the way the ConsoleAccounts function.
Add support for the EIP-165 interface or update the Safe contracts used in Brahma from 1.3.0 to the most recent version.
Context
0xsomeone (judge) decreased severity to Medium and commented:
0xad1onchain (Brahma) confirmed
0xad1onchain (Brahma) commented:
