kaspanet/rusty-kaspa

Locally built proof failed validation: the proof doesn't have sufficient blue work in order to replace the current DAG

0xtrossets opened this issue · 1 comments

Describe the bug
Can't sync with testnet-11

2024-04-19 14:53:56.400+10:00 [INFO ] Validating level 5 from the pruning point proof (2107 headers)
2024-04-19 14:53:58.509+10:00 [INFO ] Validating level 4 from the pruning point proof (2107 headers)
2024-04-19 14:54:00.835+10:00 [INFO ] Validating level 3 from the pruning point proof (2107 headers)
2024-04-19 14:54:03.109+10:00 [INFO ] Validating level 2 from the pruning point proof (2107 headers)
2024-04-19 14:54:05.386+10:00 [INFO ] Validating level 1 from the pruning point proof (2107 headers)
2024-04-19 14:54:07.933+10:00 [INFO ] Validating level 0 from the pruning point proof (2107 headers)
thread 'tokio-runtime-worker' panicked at protocol/flows/src/v5/ibd/flow.rs:318:29:
Locally built proof failed validation: the proof doesn't have sufficient blue work in order to replace the current DAG
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Exiting...

To Reproduce
Steps to reproduce the behavior:

  1. macos v0.13.6 node / linux
  2. ./kaspad --testnet --netsuffix=11 --appdir=./data

Expected behavior
Not error. Not exit.

Desktop (please complete the following information):

  • OS: MacOS Intel / linux (docker)
  • Kaspad version: 0.13.6

Edit:
Same exact issue running the linux build in docker

Fixed by #453