Skip to content

Commit

Permalink
Update pages/advanced/eip-7702/7702-safe.mdx
Browse files Browse the repository at this point in the history 
Co-authored-by: Germán Martínez <[email protected]>
  • Loading branch information
@akshay-ap @germartinez
akshay-ap and germartinez authored Dec 4, 2024
1 parent 69f3146 commit eb326df
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion pages/advanced/eip-7702/7702-safe.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ This means that the account will be created with an empty storage, and the user

Existing Safe contracts cannot be used with EIP-7702, because of following reasons:

- Delegating to Safe Singleton or the Proxy contract will expose the EOA account to the risk of front-runing during setup.
- Delegating to Safe Singleton or the Proxy contract will expose the EOA account to the risk of front-running during setup.
- In its current implementation, the Safe Singleton contract does not let itself to become an owner meaning that after delegating to the Safe Singleton, the EOA account cannot sign Safe transactions and will need to keep another private key to do so.

## Possible approaches
Expand Down

0 comments on commit eb326df

Please sign in to comment.