🔒 Loosen Runtime Bytecode Check

[QYuQianchen]

It can be an edge case, users may be interested in creating a contract without any runtime bytecode, such as deploying with 0x600060006000f0. Could implementing a check like newContract.code.length == 0 be considered overly strict in this context?

[pcaversaccio]

@QYuQianchen in the Design Principles we write the following:

• CreateX should cover most but not all contract creation use cases.

I consider deploying a zero-byte runtime bytecode in the context of CreateX rather a bug than a feature & a non-use-case, and thus we should prevent people from accidentally deploying such a bytecode. @mds1 thoughts?

[mds1]

@QYuQianchen what is the use case for that? Currently I agree with @pcaversaccio, if your deployment results in empty bytecode you likely made a mistake

[pcaversaccio]

Actually, if someone wants to do this, anyone can deploy via CreateX another factory contract that allows for a zero-byte runtime code that can be used within the same deployment transaction to deploy such a zero-byte contract. Also, I don't see any reason why a specific deployed address matters in that case. I will close this discussion accordingly.