search

vsaraph / ethereum_analysis

Analyzing historical Ethereum data.
MIT License
2 stars 0 forks source link

Regarding the issue of synchronizing Ethereum data #3

Open xuyi33333 opened 1 month ago

xuyi33333 commented 1 month ago

Hello, I noticed in your paper that you mentioned "obtained a baseline copy of the blockchain from the ConsenSys archive dating from Ethereum’s origins in 2016 to early October 2017. Starting from this base, we used the geth utilities to synchronize up to December 2017." Could you please let me know how you obtained this archive? And I'm also curious about how you used geth to continue the synchronization process. Could you please share more details on that? It seems that the information is somewhat dated, and I haven't been able to find a source for it. I would greatly appreciate your assistance.

xuyi33333 commented 1 month ago

I'm also curious about how you handled the statedb equired for executing Ethereum transactions.

vsaraph commented 1 month ago

Data was obtained via private communication through mutual contacts that I had at ConsenSys at the time. They were willing the share a copy of the data that they had with us.

geth has probably changed substantially since I've worked on this (I have not been involved in anything blockchain related for years now), but from what I can recall, it had a mode you could run it in called archive mode, which you could resume from a snapshot. We'd resumed it from the snapshot that we'd obtained from them. This required fast I/O since maintaining an archive node of Ethereum means saving all previous state.

xuyi33333 commented 1 month ago

Thanks for your reply.