-
Notifications
You must be signed in to change notification settings - Fork 565
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
warp sync without download histrocial blocks #8
Comments
Had a quick check of the code and yeah I don't think it is currently possible to not download historical block. Can we change that? |
I abused |
cc @bkchr |
I still need to write some issue. I would say that we currently should disable blocks pruning at all. We need some more features to have this working properly. Otherwise we may loose block history. |
My goal is to setup lightweight bootnodes that doesn't require too many resources (mostly disk) so we can have multiple of them distributed in different hosts. We have other RPC nodes to archive all blocks and states. |
Yes, but the problem is that if enough people are running with blocks pruning other people needing to find these archive nodes in the network. |
Could you explain a bit? Because otherwise I don't think the right solution is don't allow people to run lightweight node. |
Something like this: #523 |
Any docs about it? Can't find them.
To my understanding, it will download finality proof and put the best block to latest block and download historical blocks.
Is it possible to not download historical blocks? I tried with
--blocks-pruning=128 --state-pruning=128
and that doesn't seem to have any impacts.Basically I want to minimize the resource requirement of a parachain node and I don't want to download and store all the relaychain data.
The text was updated successfully, but these errors were encountered: