So I don't have good news: the sync with the bootstrap got stuck again on the same block, and today I ran a full sync (again from scratch) from the network, and stuck again on the same block:
ERROR: AddToBlockIndex() : Rejected by stake modifier checkpoint height=254838, modifier=0xbbb66c4098c49e9b
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
ProcessBlock: ORPHAN BLOCK, prev=de6a01927d66274b854a
ProcessBlock: ORPHAN BLOCK, prev=29d73af5cbccbbbedc1d
ProcessBlock: ORPHAN BLOCK, prev=2a51d754c9f50b4e3776
ProcessBlock: ORPHAN BLOCK, prev=23d34862301c7669adc4
ProcessBlock: ORPHAN BLOCK, prev=0599c70edf9b828539ad
ProcessBlock: ORPHAN BLOCK, prev=88c5d5fb47f3ef061440
ProcessBlock: ORPHAN BLOCK, prev=b6f08adaeaab90140771
After the "AcceptBlock FAILED" on block 254838, all new blocks are considered orphans (and that has been running for a while). It never passed that block regardless of how long I waited (which makes sense if it believes that block is faulty - it can't accept the next blocks because the chain is broken). There must be something wrong with that block (or much more with the checking algorithm in the client - I have no time to investigate that right now).
It could be good if you could let the dev check on the code and the block to make sure there is no problem there.
Client pulled from git Debug branch, showing version 2.0.2.4-g.
My europecoin.conf:
connect=stratum.infernopool.com
connect=23.227.190.77
connect=194.135.93.49
connect=194.135.92.209
connect=104.255.33.55
I don't believe this could come from my wallet.dat. I'm launching another sync with a brand new wallet.dat just in case (and with the nodes that are posted in the announcement for this post which I just saw are different from the ones I was using, and I believe I took from the dump of the new client), but I don't have much hopes since it seems I have the exact same problem than wildduck on
that post. At least that's coherent.
Any ideas welcome!
Thanks,
JY.
first, now yo have the right client and configuration. Now you just need a bit more patient, because there are chunks in the chain, that due to our mildly wild history, are looking strange and like beeing stuck. Akso because of this history, some functions are altered or disabled, over a certain amount of blocks and not managed the engine (they are hardcoded) and this fact also makes the chain report orphans during those blocks. But anyway starting with afresh wallet.dat doesn't do any harm, you can go with it. many user during this release have experienced that and also have been like "no i am stuck" (you can see some all over the last ten pages. and they all got over it. When a chain syncs, it tells the whole story, of the coins history. For example the fact Europecoin has been dead for half a year, produces on some areas of the chain outputs, that are looking exactly like that. you will see similar behaviour in the area, where the hart-fork happened and so on. I recommend to not interrupt the wallet to often and to make regular use of the "repairwallet" function via the console.
keep me up to date
@halibit @woody did one of the download options work for you?
have fun
Matthias
EDIT also read Chris post he answered too and our posts crossed.
.