There's currently a bug in status-go whereby it incorrectly reacts to history node confirmations.
The way we need to address this is to first disable them, deploy the code changes, and once all the client have upgraded, re-enable them.
This commit disables confirmations for all the hosts.
It should not have any impact on clients when deployed.
There's currently a bug in status-go whereby it incorrectly reacts to history node confirmations. The way we need to address this is to first disable them, deploy the code changes, and once all the client have upgraded, re-enable them.
This commit disables confirmations for all the hosts. It should not have any impact on clients when deployed.
cc @vkjr