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
I believe, based on the ethereum ABI spec and confirmed using Remix, that the function selector should be computed using the string "function" for function types and that "function" shall be used in the ABI json as well, and not "bytes24", despite function types having an identical encoding to bytes24 in the calldata. I believe 4byte is also incorrectly using "bytes24" to compute the selector.
The text was updated successfully, but these errors were encountered:
I believe, based on the ethereum ABI spec and confirmed using Remix, that the function selector should be computed using the string "function" for function types and that "function" shall be used in the ABI json as well, and not "bytes24", despite function types having an identical encoding to bytes24 in the calldata. I believe 4byte is also incorrectly using "bytes24" to compute the selector.
The text was updated successfully, but these errors were encountered: