Skip to content
This repository has been archived by the owner on May 13, 2022. It is now read-only.

[Dump] Catchup block 0 #1145

Closed
gregdhill opened this issue Jun 16, 2019 · 1 comment
Closed

[Dump] Catchup block 0 #1145

gregdhill opened this issue Jun 16, 2019 · 1 comment

Comments

@gregdhill
Copy link
Contributor

With a dump-restore, previous events are stored in block zero which is an issue when catching up a node as Tendermint will not replay this block, resulting in an appHash collision.

@silasdavis
Copy link
Contributor

The idea with restore is that we explicitly do not pay for consensus on transactions committed in a previous chain, so Tendermint not gossiping those is as-designed.

Effectively on a restore chain genesis == genesis doc + dump state. They should be distributed together

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

2 participants