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
We currently use revert(0,0) in a couple of scenarios that should be formated as panics ( keccak256(Panic(uint256)))
Currently available panics are
0x01: Using assert.
0x11: SafeMath over-/under-flows.
0x12: Divide by 0.
0x21: Conversion into non-existent enum type.
0x22: Incorrectly encoded storage byte array.
0x31: pop() on an empty array.
0x32: Index out of bounds exception.
0x41: Allocating too much memory or creating a too large array.
0x51: Calling a zero-initialized variable of internal function type.
How can it be fixed
🤖
The text was updated successfully, but these errors were encountered:
I think we can close this even if we don't have implemented all of them yet. We do have the mechanics in place and are using panic/error codes whenever it is appropriate.
What is wrong?
We currently use
revert(0,0)
in a couple of scenarios that should be formated as panics (keccak256(Panic(uint256))
)Currently available panics are
0x01: Using assert.
0x11: SafeMath over-/under-flows.
0x12: Divide by 0.
0x21: Conversion into non-existent enum type.
0x22: Incorrectly encoded storage byte array.
0x31: pop() on an empty array.
0x32: Index out of bounds exception.
0x41: Allocating too much memory or creating a too large array.
0x51: Calling a zero-initialized variable of internal function type.
How can it be fixed
🤖
The text was updated successfully, but these errors were encountered: