Skip to content
This repository has been archived by the owner on Feb 16, 2025. It is now read-only.

Setting pruning="nothing" in app.toml results in node falling out of consensus #197

Open
mdyring opened this issue Sep 28, 2022 · 0 comments
Assignees
Labels
bug Something isn't working consensus-breaking

Comments

@mdyring
Copy link
Contributor

mdyring commented Sep 28, 2022

How to reproduce:

  1. Install v1.1.4
  2. Set pruning="nothing" in app.toml
  3. Start emd

Example output:

{"level":"info","module":"consensus","time":"2022-09-27T22:02:16Z","message":"Replay last block using real app"}
Error: error during handshake: error on replay: wrong Block.Header.AppHash.  Expected 5D57DB156791E0D497E4AFC0C4F077B8DB6BBC6458D6DA5C21CE51918C8141DB, got 53F2CCB248B8B426E74CFD9647AFC2CE1341838E479F69422C8EFB2734DFC901
@mdyring mdyring added bug Something isn't working consensus-breaking labels Sep 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working consensus-breaking
Projects
None yet
Development

No branches or pull requests

2 participants