Please unmark invalid blocks upon restart
It happens very often that people forget to update their nodes in time for a hard fork, and they update after the fork is done.
Unfortunately this does not solve the problem for them because the previous (old) node marked as invalid all new blocks and the release will not process them, staying stuck.
The node operators must manually find invalid blocks by hand and do a "reconsiderblock" on them, to allow the node to follow the right chain.
To solve this problem I suggest to unmark or delete bad blocks upon restart in order to let them validate against a newer release of the client, so that an upgrade of the node software after a fork will let node operators to get on the new chain in an automated manner.
Would be useful!
PS C:\Program Files\Bitcoin-abc\daemon> .\bitcoin-cli.exe invalidateblock 000000000000000001b4b8e36aec7d4f9671a47872cb9a74dc16ca398c7dcc18 .\bitcoin-cli.exe : error: Could not locate RPC credentials. No authentication cookie could be found, and RPC password is not set. See -rpcpa ssword and -stdinrpcpass. Configuration file: (C:\Users\Administrator\AppData\Roaming\Bitcoin\bitcoin.conf) 所在位置 行:1 字符: 1
- .\bitcoin-cli.exe invalidateblock 000000000000000001b4b8e36aec7d4f967 ...
-
+ CategoryInfo : NotSpecified: (error: Could no...n\bitcoin.conf):String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError
window x64,how to ?
@trybye It helps me:
- Run bitcoin-qt.exe;
- Then run "bitcoin-cli.exe reconsiderblock BLOCK_HASH";
- Restart bitcoin-qt.exe.
Perhaps it will help you too. Good luck!