Fix: Verify there are no critically breaking hash collisions with alternative ABI codecs
Alexangelj opened this issue · comments
Description
Hyper accepts custom encoded function calls via the fallback function. The first four bytes of these data packets could match a function signature. This would then cause Hyper to go into the function's execution instead of the intended fallback function.
To verify this is not a problem, we must export a list of all function signatures and the possible collisions that could be caused with certain alternative codec calls.