Use nano consensus instead of fake-pico to fix issues that appeared on fake-pico when staying connected for longer time.
Most sigificantly after some time calls to _getAccounts in the nano api do neither return nor throw but keep pending forever.
The issues seem to arise after a warning PeerChannel: Error while processing 'accounts-proof' message from ...: TypeError: Cannot read property 'accountsHash' of null is visible in the console.
This does not happen in the testnet though. Thus, the issue might be related to connecting to additional peers after the pico peers (note that in testnet there is only one additional seed node besides the pico peers, while in mainnet there are many more).
However, as the real pico consensus is hopefully coming soon, for now I reverted the safe to using nano consensus.
Use nano consensus instead of fake-pico to fix issues that appeared on fake-pico when staying connected for longer time. Most sigificantly after some time calls to
_getAccountsin the nano api do neither return nor throw but keep pending forever. The issues seem to arise after a warningPeerChannel: Error while processing 'accounts-proof' message from ...: TypeError: Cannot read property 'accountsHash' of nullis visible in the console. This does not happen in the testnet though. Thus, the issue might be related to connecting to additional peers after the pico peers (note that in testnet there is only one additional seed node besides the pico peers, while in mainnet there are many more).However, as the real pico consensus is hopefully coming soon, for now I reverted the safe to using nano consensus.
Requires https://github.com/nimiq/network/pull/10 to be approved and packaged first.
This change is currently already deployed.