EIPs
EIPs copied to clipboard
AUTH_USURP: Publishing code at an EOA address
Opening a draft for a proposed opcode that would allow publishing code at an EOA's address, converting it into a contract account, one way.
The specific proposed implementation is still under development, but this can serve as a starting point for discussion.
It is currently likely this will utilize the AUTH opcode as defined in 3074 (which will need to be split into an abstract-EIP), and then allow the authorized contract to perform a CREATE-like operation that target's the EOA's address for the new code publication.
All tests passed; auto-merging...
(pass) eip-5003.md
| classification |
|---|
updateEIP |
- passed!
I guess I need to wait to be assigned an EIP number before I can fix the bot's complaints.
Changes accepted. Thanks, @MicahZoltu.
The commit 27d9b4cf8ee32de8c7f03f1c3b229bc958ef8760 (as a parent of 1ccafdf7198d14f418036a9a608ebddab98c1a1f) contains errors. Please inspect the Run Summary for details.