Topic: incoming connections with -reindex-chainstate (Read 193 times)
Most likely the client only upload blocks which already verified (which means only uploading data which isn't corrupted).
If you're reindexing it's likely broadcasting the height of the reindexed chain and not the old one so it can be ignored.
If not, if its been 10 minutes since you started, there's a good chance you no longer have the longest chain and so your block data won't be sent to anyone anyway. Even if the blocks were corrupted, the core verifies blocks anyway (hence why reindexijg takes longer than the time it takes to download the data in raw form)...
If not, if its been 10 minutes since you started, there's a good chance you no longer have the longest chain and so your block data won't be sent to anyone anyway. Even if the blocks were corrupted, the core verifies blocks anyway (hence why reindexijg takes longer than the time it takes to download the data in raw form)...
needed to re-start bitcoind with -reindex-chainstate. i noticed that the server is accepting incoming connections. i would think it would hold off incoming connections until finished with the reindex. why upload data if there has been some possible data corruption.
should i disable listening manually?
should i disable listening manually?
Jump to: