Skip to content
This repository has been archived by the owner on Aug 14, 2023. It is now read-only.

Overhaul the SVM database architecture to allow for light clients, Merkle proofs, root cryptographic signatures #492

Open
neysofu opened this issue Feb 16, 2022 · 0 comments
Labels
medium Medium-sized task refactoring Refactoring svm

Comments

@neysofu
Copy link
Contributor

neysofu commented Feb 16, 2022

While the current design works and has good performance, its capabilities are quite limited. We should switch to a data structure that allows for Merkle proofs, and root cryptographic signature validation. AFAIK, the current state of the art is Erigon. Most of the changes would be limited in scope to svm-state, without affecting the rest of the system. Here's some useful links:

https://eips.ethereum.org/EIPS/eip-3102

https://www.youtube.com/watch?v=aAZoiJIQiTE

This issue replaces two older, separate issues (#328, #329).

@neysofu neysofu changed the title Overhaul the SVM database architecture to allow light clients, Merkle proofs, root cryptographic signatures Overhaul the SVM database architecture to allow for light clients, Merkle proofs, root cryptographic signatures Feb 16, 2022
@neysofu neysofu added medium Medium-sized task refactoring Refactoring svm labels Feb 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
medium Medium-sized task refactoring Refactoring svm
Projects
None yet
Development

No branches or pull requests

1 participant