Research: Post-EOF source code verification

[kuzdogan]

EOF (Ethereum Object Format) is slowly coming... It will change the bytecode format drastically, and hopefully for good, and we need to prepare, not only as just Sourcify, but as the whole verification ecosystem.

The goal should be to dive deep into EOF and understand its impact on source code verification. The owner of this task and the others can share the knowledge under this issue, and consult others when necessary. We can discuss how we should move forward with the necessary changes too.

One important thing to come up from this research should be how Solidity will and should handle the CBOR metadata. AFAIK this is still TBD and if we understand EOF well, we can still be able to contribute to its format and structure. Some other specifics to understand are how libraries, immutables, call protection, and constructor arguments are structured.

Finally, I think it will be really valuable to share this knowledge as a blog post to the whole ecosystem. Another thing I've been thinking about is maybe come up with a "EOF visualizer" tool. Since the EOF code will be structured, I think it will be quite useful to have a website where you paste the raw bytecode and it will visualize the code containers, metadata etc.

Note that this might end up being longer than a 2-week task.