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
vyper Version (output of vyper --version): 90e3d20
Python Version (output of python --version): v3.8.10
What's your issue about?
while implementing create() and create_copy_of() (see #2889), i realized that CREATE and CREATE2 opcodes don't bubble up failure of the initcode, instead they return a zero address. for safety, i decided the implementation should check the zero address case. but, the existing implementation of create_forwarder_to() (see below) does not check for the zero case. i'm actually not sure what the ideal behavior here is, because if there is a collision, it most likely means that the code you intended to deploy is already deployed.
Version Information
vyper --version
): 90e3d20python --version
): v3.8.10What's your issue about?
while implementing
create()
andcreate_copy_of()
(see #2889), i realized thatCREATE
andCREATE2
opcodes don't bubble up failure of the initcode, instead they return a zero address. for safety, i decided the implementation should check the zero address case. but, the existing implementation ofcreate_forwarder_to()
(see below) does not check for the zero case. i'm actually not sure what the ideal behavior here is, because if there is a collision, it most likely means that the code you intended to deploy is already deployed.vyper/vyper/builtin_functions/functions.py
Lines 1731 to 1741 in 90e3d20
How can it be fixed?
The text was updated successfully, but these errors were encountered: