-
Notifications
You must be signed in to change notification settings - Fork 950
Issues: safe-global/safe-smart-account
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Provide a way to identify whether a contract is a SAFE.
future
Features for next major contract version
#714
opened Dec 12, 2023 by
MicahZoltu
Fallback function could be made payable.
future
Features for next major contract version
#712
opened Dec 9, 2023 by
MicahZoltu
Extend Safe With Additional Signing Schemes
future
Features for next major contract version
#698
opened Nov 10, 2023 by
nlordell
MultiSendCallOnly can be further optimized to save gas
future
Features for next major contract version
#372
opened Dec 23, 2021 by
skeletor-spaceman
Feature request: Transaction meta data
future
Features for next major contract version
#331
opened Aug 11, 2021 by
tschubotz
Make transaction order flexible
future
Features for next major contract version
#199
opened Apr 19, 2020 by
rmeissner
Remove payment logic from core contract
future
Features for next major contract version
#197
opened Apr 18, 2020 by
rmeissner
Signatures that depends only on Features for next major contract version
msg.sender
are nonce independent.
documentation
future
#187
opened Apr 1, 2020 by
rmeissner
Naming of functions for adding/removing owners is not coherent
future
Features for next major contract version
#118
opened Aug 8, 2019 by
Uxio0
ProTip!
Follow long discussions with comments:>50.