You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
I'm not sure if this is the correct place to raise this issue. You may give me the correct repo if this isn't.
While using safe to manage a timelock, I encountered an issue.
Safe dont allow users to input empty string.
When the type is bytes we can still enter 0x, but when the type is string, safe requires it to be non-empty, but there is of course a need to pass empty string. For example in aave's timelock contract the signature parameter can be empty string
To solve this currently I have to use Custom Data
The text was updated successfully, but these errors were encountered:
I'm not sure if this is the correct place to raise this issue. You may give me the correct repo if this isn't.
While using safe to manage a timelock, I encountered an issue.
When the type is
bytes
we can still enter0x
, but when the type isstring
, safe requires it to be non-empty, but there is of course a need to pass empty string. For example in aave's timelock contract the signature parameter can be empty stringTo solve this currently I have to use
Custom Data
The text was updated successfully, but these errors were encountered: