Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proof of concept for code chunk tracking. #62

Open
pipermerriam opened this issue Jun 16, 2021 · 1 comment
Open

Proof of concept for code chunk tracking. #62

pipermerriam opened this issue Jun 16, 2021 · 1 comment
Labels
help wanted Extra attention is needed

Comments

@pipermerriam
Copy link
Contributor

pipermerriam commented Jun 16, 2021

One sub-component of "State Expiry" and the underlying changes to the storage layout within the trie are that code will now be chunked and stored within the trie itself.

https://notes.ethereum.org/@vbuterin/verkle_tree_eip#Code

One thing that we want to verify is that tracking code chunk access will indeed be relatively trivial. Write a quick POC in a client that tracks code chunk access using something like the bitfield approach suggested by Vitalik on the call. (see call recording about 20-30 minutes into the call). Is it indeed trivial to implement? Are there any hidden complexities?

Suggested methodology for this would probably be to run a modified client, though it is possible the necessary information is available through the transaction tracing APIs as well.

@pipermerriam pipermerriam added the help wanted Extra attention is needed label Jun 16, 2021
@ogenev
Copy link
Contributor

ogenev commented Jun 23, 2021

I'm going to take a stab on this issue. For reference, I will keep my notes and updates here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants