styppo

- [ ] Synchronize mempool **after** consensus is established - [ ] Implement mechanism to incrementally request the full mempool

Could not parse request type ID

5

CI run: [#2244](https://github.com/nimiq/core-rs-albatross/actions/runs/2229153753) Job: `LowViewChangeDelay` Node: `validator1`-`validator4`, `spammer` Logs: [2244 LowViewChangeDelay.zip](https://github.com/nimiq/core-rs-albatross/files/8580781/2244.LowViewChangeDelay.zip) ``` 2022-04-26T20:44:41.120032Z ERROR network | [Request ID 6527] Could not parse request type ID, swarm task{peer_id=PeerId("12D3KooWMBzxH8EdKT7mGwjftCuW3gN6fvACfx43Mg6J3tRt9iqc")} 2022-04-26T20:44:41.120239Z ERROR network...

Handle change of a validator's PeerId

2

The validator network cannot handle a validator changing its PeerId (e.g. by erasing its on-disk peer key as done in the EraseState test scenario), so no further communication is possible...

The current gossipsub topic structure for block propagation suffers from poor mesh quality on the `block-header` topic, duplicated messages due to re-publishing as well as data duplication across topics. This...

In [this CI run](https://github.com/nimiq/core-rs-albatross/actions/runs/9929244435/job/27426574778), it was observed that validators 2 and 4 fail to catch up after being restarted. It appears that unknown blocks received from head requests are not...

We can see this happening in the ValidatorStress scenario