Consensus is not initialized when running the network from genesis block about dusk-blockchain

[jules]

However, in case of starting the network from genesis block, wouldn't the network get stuck as no node is able to generate block at height 1?

This can be worked around by using the internal walletgenesis.dat, which is currently kept in dusk-buddy. The wallet has a stake and bid attributed to it in block 0, so that it can bootstrap the consensus by itself and allow others to join. A wallet file can be specified with -w I believe, if using the spawner script.

Note by the way, that the patch you suggest would be moot if #25 were merged. It should allow for the generation component to start on it's own as a bid would be found, and the provisioner components to be started automatically as searching for stakes was removed, since it was deemed unnecessary.

[ggoranov]

This can be worked around by using the internal walletgenesis.dat, which is currently kept in dusk-buddy. The wallet has a stake and bid attributed to it in block 0, so that it can bootstrap the consensus by itself and allow others to join. A wallet file can be specified with -w I believe, if using the spawner script.

The local network has a node that loads the genesis wallet. But it does not initialize the consensus as msg.InitializationTopic is never published.

[jules]

The local network has a node that loads the genesis wallet. But it does not initialize the consensus as msg.InitializationTopic is never published.

That's correct, my mistake. Even with #25 merged, it would still need to see at least one block before starting up, so the patch should take care of it.