Albert Callarisa
Albert Callarisa
There's already another node in the same network before I trigger the genesis validation. Maybe this is the reason?
In my tests I start with 1 validator (genesis) and add 10 more at once. Maybe I can try adding them one by one better?
/cc @JekaMas @rgeraldes
I think I have more details. There were some nodes running 2.0.1 with some new blocks (like 200 blocks). There was one node with old blocks (like 150k blocks) that...
if the reason is related with the node with more blocks, I wouldn't bother. It's quite unlikely to happen on an ongoing network
I think this is something we should cover in unit tests first. But you're right we could have an e2e test that simulates some kind of fork and puts some...
This issue can be closed once we have a PR implementing the fix and a unit test for it, don't you think?
/cc @rgeraldes
[logs.txt](https://github.com/kowala-tech/kcoin/files/2427372/logs.txt) Here the logs, it happened again. I suspect the validator tries to join too early: ``` .... WARN [09-28|08:11:58.388] Joining the network 2 with a deposit 1000000000000000000000000. Account "0xa4A06cb7BCaA0162082F170d4B6f4b5360DA9e11"...
The `SyncWaiter` receives a `downloader.DoneEvent` even though the `eth.blockNumber` is 0 and `admin.peers` is empty.