I’m looking into using Tendermint for a new project of mine, but I have a question about block pruning and state sync.
In my application, holding a long-term ledger is not a requirement. It’s OK if we can’t trace all blocks to genesis, and it’s OK if we lose that chain because no nodes have kept those blocks. Low resource usage is the priority, while not sacrificing the effectiveness of the consensus protocol.
My question was whether or not it’s possible to have this scenario succeed:
- Start a new cluster with one node
- The cluster continues to operate from that one node and it only holds the last, say, 1000 blocks.
- Soon the node no longer has the blockchain all the way to genesis because of prune blocks.
- I add a new node to the cluster and State Sync is used to catch up to the current state and then begin normal consensus
- I now have two nodes connected to the cluster and I can later add and remove more with a similar process, all without needing to have a node that has the full blockchain state.
My biggest concern is this piece in the docs:
This says that 2 RPC servers are required to do a state sync, but what if I start out with a cluster with only one node? This is particularly possible in my use-case because my use-case is a permissioned chain that should operate remotely similar to a scalable database which can function fine with only one node.
I see that in the latest release of Tendermint you can now do a State Sync over RPC. Does that mean that you no longer need 2 RPC servers, and you could join a second node to a cluster that started with only one node that doesn’t have the full ledger?