Richard Meissner
Richard Meissner
Signing messages allows to authenticate a user. This can be used in Safe apps to identify/ authenticate the connected wallet. Currently it is not possible to request a signature from...
Currently https://github.com/gnosis/safe-contracts/blob/main/docs/error_codes.md only mentions a short error description. It would be helpful to add reasons why specific errors code occur and how to debug/ solve them
Currently there are not tests for EIP-1271 support or nested Safes. Only related test is related to an 0x Exploit: https://github.com/safe-global/safe-contracts/blob/da66b45ec87d2fb6da7dfd837b29eacdb9a604c5/test/integration/GnosisSafe.0xExploit.spec.ts#L77
Currently the transactions need to be executed in strict order of the nonce (as a normal ethereum transaction). This was done to save gas and to ensure that specific actions...
## Context / issue Some token standards are not handled in the `DefaultCallbackHandler` and should be added: - https://eips.ethereum.org/EIPS/eip-1363 - https://github.com/ethereum/EIPs/issues/677 - https://github.com/ethereum/EIPs/issues/223 ## Proposed solution Add corresponding callbacks to...
Essentially when the `msg.sender` is an owner and the Safe has a threshold one, the nonce is never checked. This is because in this case the check on contract level...
Currently the payment logic is an essential part of the core contract. It should be possible to extract this into a lib that can be used via a delegate call....
With geth it is already possible to inject code at an address, thus it is not required anymore that we ship contract code that should only be called off-chain. For...
The documentation should be update for 1.3.0 and the natspecs should be improved so that they can be used properly
We should add tests for all kind of integrations/ e2e flows to make sure that they work. Note: Some tests will be deprecated with the migration to hardhat and should...