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
A Gelato deposit transaction is decoding the transaction as fallback(), which prevents us from properly auditing the inputs.
I am unsure if this is an issue in indexing the implementation, or if the implementation changed and Safe is not picking that up (which may be tangentially related with safe-global/safe-transaction-service#2344 (comment) where it was noted proxies are tough.)
Date and time this happened or you first noticed this issue
Issue Category
Other
What happened?
We've created two transactions, both that target proxies.
Our USDC approve transaction is properly decoded as
approve()
A Gelato deposit transaction is decoding the transaction as
fallback()
, which prevents us from properly auditing the inputs.I am unsure if this is an issue in indexing the implementation, or if the implementation changed and Safe is not picking that up (which may be tangentially related with safe-global/safe-transaction-service#2344 (comment) where it was noted proxies are tough.)
Date and time this happened or you first noticed this issue
01-06-2024
Network
Polygon
Safe Address
0xe37dD9A535c1D3c9fC33e3295B7e08bD1C42218D
Token Address
No response
Token Type
None
Transactions
The text was updated successfully, but these errors were encountered: