Is there any bantime option or similar to avoid this???
>> Height = 36946, nStakeModifierChecksum = 429f417a
>> nHeight = 36946, nPoWHeight = 19048
SetBestChain: new best=00000000162a0d8028ed34f73de7b9cfa0a17248efc8cacb02699819a6fc72f4 height=36946 trust=2799568249269362 blocktrust=47101854158 date=05/20/17 14:10:07
ProcessBlock: ACCEPTED
received block d20703380ceaad85b3cc
ProcessBlock: ORPHAN BLOCK, prev=0000000006cf06bce3a6
received block 0000000002bedfcec8f8
ProcessBlock: ORPHAN BLOCK, prev=d20703380ceaad85b3cc
received block 0000000008df666c3f93
ProcessBlock: ORPHAN BLOCK, prev=0000000002bedfcec8f8
received block d25679ceed8f471789a5
ProcessBlock: ORPHAN BLOCK, prev=0000000008df666c3f93
received block bf39411c5e788077e88f
ProcessBlock: ORPHAN BLOCK, prev=d25679ceed8f471789a5
received block 00000000135b6dc989cf
ProcessBlock: ORPHAN BLOCK, prev=bf39411c5e788077e88f
received block 00000000087806762670
ProcessBlock: ORPHAN BLOCK, prev=00000000135b6dc989cf
received block 000000000b26a3ead3f1
ProcessBlock: ORPHAN BLOCK, prev=00000000087806762670
received block 00000000188d37b1dd56
ProcessBlock: ORPHAN BLOCK, prev=000000000b26a3ead3f1
received block 00000000079a28891063
ProcessBlock: ORPHAN BLOCK, prev=00000000188d37b1dd56
received block 0000000014bcf410177f
ProcessBlock: ORPHAN BLOCK, prev=00000000079a28891063
received block 0d168fbdb32b5fa37985
ProcessBlock: ORPHAN BLOCK, prev=0000000014bcf410177f
received block 38c74ff63393e1907bb3
After 36946 network is sending my wallet only orphan blocks. Lots of them... Is there any bantime or similar option to ban nodes which send orphan blocks???
The privacy characteristics of the coin make it very interesting, but it's the coin in which I have found more problems to sync in 4 years in crypto. Not a good signal...
Salute
Salute
no ...
i have no idea what you mean by a 'ban time' ...
it has been explained in an earlier post / response ...
the orphan blocks ALWAYS exists in ANY network ... and also explained before - but here it is again ... you are correct in saying this is more than others currently ... but ONLY others that have NOT forked ...
this coin forked after the first sweepstake block was found ... almost ANY coin that forks WILL have large numbers of orphan blocks that exist ... this coin is no exception ... many many MANY orphan blocks ... the wallet / daemon tries to find another node to download from - and continues to do so after a large number of orphan blocks - but EVERY node it comes across will have the same situation ... so it will continue to download the orphan blocks until the next valid block is downloaded in the blockchain ... when that happens - the rest of the blockchain is just a matter of time ...
not intending on sounding rude in anyway - but repeating myself - and others repeating themselves on the SAME issues that have been posted before - is quite monotonous and a complete waste of time for everyone involved ...
PLEASE READ the previous posts ... or even use the forum search bar in top right hand corner that bitcointalk have ...
in any case - thats the reason ... so again PATIENCE is a virtue you will need to download the blockchain from scratch - even if you are using a bootstrap ...
hope that helps ...
#crysx