-
Notifications
You must be signed in to change notification settings - Fork 303
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
Spec out FastSync and StateSync #273
Comments
I think, it makes sense to at least consider writing a custom block-sync (aka fast-sync) reactor using libp2p instead of modifying the current blockchain reactors: Alternatively, and the first thing we should investigate thoroughly: we could make the blockchain reactor load the block data from the IPFS data store instead of the tendermint store - which will only store headers moving forward: #182. We'd have to make sure, that this works with the different kinds of validator nodes though. DAS light validator nodes would only care about the headers + DAS sampling for instance so they would not run the blockchain reactor but would still run the consensus reactor. Given that the blockchain reactor looks kinda horrible and the v2 is still not stable (ref: #309) and also not really straightforward to understand, we should probably write our own block-sync protocol in the long run. We should first think through if we can leverage the existing one first though as it is used in production for several years now. |
ref: #191 |
Closing this for now. We will use tendermint more as a black box. in case we later merge core and celestia node into one node repo, this becomes relevant again. |
Will add more details shortly
The text was updated successfully, but these errors were encountered: