I am on 261655.
getblockhash 261655
b187c860bf073423914955ed4ef35fe42135547446ecfa73dbc1dd4944caf088
lol
getblockhash 261655
c90edb6fc9b9b5379293aa98dab394a6437e5ef5a0fafb9d3e8213b59dca7927
not good .....
just assume we on the right one and hes on the wrong one
my masternodes are on different one =/
well a lot of my masternodes show
/darknet-cli getblockhash 261655
4eb4f0301155f55a64842e01bc7b59772eed45d5ec332a7518d488fc824eb308
so i guess we are f**** anyway ....
shuting down my wallets and waiting for proper fix now.
great! all the stakes are mine .
More seriously what is going wrong with the forks? Would it possible for other players to deliberately try to sabotage DNET? This is coin is so promising that I wouldn't rule out this possibility. But in all events we need a more robust code able to keep us all on one constant chain and able to pass the dreaded block 260832 from peers syncing... and not from the block file.
May the code be with you dear Devs and our patience be awesomely rewarded .