BTS 0.8.1 is forking

[svk]

Just woke up to find that my delegate had lost all connections once again!

[cube]

delete your data folder keep your wallet and redownload chain, its faster now... BM also had to do this, I did and now I think im on the right chain.

I removed the chain and redownloaded.  After a long while, it resynced and was back to the main chain.  But it just went into the wrong chain yet again.  How to avoid getting into a fork?  How to recover from a fork quickly?

had you deleted the "peers.leveldb" folder when you removed the chain ?
if not ,try it

Yes, I did.  And it did not really help.

If you're on version 8.1 and you re-synched, we don't really expect it to happen again, so we need to see your logs. Can you zip up your p2p.log file and post it somewhere for us to look at?

I removed the whole .BitShares folder, except wallets subfolder, for the current resync.  If it happened again, I would send the log.

[dannotestein]

delete your data folder keep your wallet and redownload chain, its faster now... BM also had to do this, I did and now I think im on the right chain.

I removed the chain and redownloaded.  After a long while, it resynced and was back to the main chain.  But it just went into the wrong chain yet again.  How to avoid getting into a fork?  How to recover from a fork quickly?

had you deleted the "peers.leveldb" folder when you removed the chain ?
if not ,try it

Yes, I did.  And it did not really help.

If you're on version 8.1 and you re-synched, we don't really expect it to happen again, so we need to see your logs. Can you zip up your p2p.log file and post it somewhere for us to look at?

[cube]

delete your data folder keep your wallet and redownload chain, its faster now... BM also had to do this, I did and now I think im on the right chain.

I removed the chain and redownloaded.  After a long while, it resynced and was back to the main chain.  But it just went into the wrong chain yet again.  How to avoid getting into a fork?  How to recover from a fork quickly?

had you deleted the "peers.leveldb" folder when you removed the chain ?
if not ,try it

Yes, I did.  And it did not really help.

[btswildpig]

delete your data folder keep your wallet and redownload chain, its faster now... BM also had to do this, I did and now I think im on the right chain.

I removed the chain and redownloaded.  After a long while, it resynced and was back to the main chain.  But it just went into the wrong chain yet again.  How to avoid getting into a fork?  How to recover from a fork quickly?

had you deleted the "peers.leveldb" folder when you removed the chain ?
if not ,try it

[cube]

delete your data folder keep your wallet and redownload chain, its faster now... BM also had to do this, I did and now I think im on the right chain.

I removed the chain and redownloaded.  After a long while, it resynced and was back to the main chain.  But it just went into the wrong chain yet again.  How to avoid getting into a fork?  How to recover from a fork quickly?

[jsidhu]

delete your data folder keep your wallet and redownload chain, its faster now... BM also had to do this, I did and now I think im on the right chain.

[xeroc]

maybe with the "checkpoints.json" file (see above) .. can't tell ..

BM stated somewhere that he had to reset the chain-folder

[cube]

confirming main chain

Code: [Select]

blockchain_get_block 2117977
{
  "previous": "ade121bc11a8a05d75e1089f5185b6a45905ac91",
  "block_num": 2117977,
  "timestamp": "2015-03-25T10:24:20",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
  "next_secret_hash": "ce025dbda2034e7de6d03664b8e80eadb057dc42",
  "previous_secret": "3ab66005d6814ac3505c81045eba7e68bbeeb639",
  "delegate_signature": "20248cc81adc718234f6c18584dd2a4e85e5b2a31c8b9b0cd5a096933a07c3cb914abd9d4acedf77b51c49505bf1d0e4b753d114f576b9a8c070a842d5fc1b29ae",
  "user_transaction_ids": [],
  "id": "1f9cdf643f1e21af79a18fe35751cd1593252014",
  "block_size": 166,
  "latency": 0,
  "signee_shares_issued": 150000,
  "signee_fees_collected": 13860,
  "signee_fees_destroyed": 448141,
  "random_seed": "c8f24a8127e2f8d782830623f27c6e84a213566b",
  "processing_time": 91567
}


Is there a simple and quick way to bring a delegate on a forked chain back to the main (besides removing the chain folder and resyn)?

[arubi]

Why is this a problem?
Isn't this the perfect time to hire some delegates? 

[xeroc]

confirming main chain

Code: [Select]

blockchain_get_block 2117977
{
  "previous": "ade121bc11a8a05d75e1089f5185b6a45905ac91",
  "block_num": 2117977,
  "timestamp": "2015-03-25T10:24:20",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
  "next_secret_hash": "ce025dbda2034e7de6d03664b8e80eadb057dc42",
  "previous_secret": "3ab66005d6814ac3505c81045eba7e68bbeeb639",
  "delegate_signature": "20248cc81adc718234f6c18584dd2a4e85e5b2a31c8b9b0cd5a096933a07c3cb914abd9d4acedf77b51c49505bf1d0e4b753d114f576b9a8c070a842d5fc1b29ae",
  "user_transaction_ids": [],
  "id": "1f9cdf643f1e21af79a18fe35751cd1593252014",
  "block_size": 166,
  "latency": 0,
  "signee_shares_issued": 150000,
  "signee_fees_collected": 13860,
  "signee_fees_destroyed": 448141,
  "random_seed": "c8f24a8127e2f8d782830623f27c6e84a213566b",
  "processing_time": 91567
}


[spartako]

I am in the main fork (77.69% participation) try to remove the chain directory (~/.BitShares/chain/) and change the checkpoints.json in this way (added a recent block in main chain) and restart the client:

Code: [Select]

[[
    2117977,
    "1f9cdf643f1e21af79a18fe35751cd1593252014"
  ],[
    2104000,
    "147f68b04701f176cab47a512430c9a82c78e217"
  ],[
    2071001,
    "58847f93f0d1846cb9250d7ba342bebda6e698e4"
  ],[
    991701,
    "2e48f0a16d2107b9ab3d1c87e803ee70d3c91ce0"
  ],[
    640001,
    "11c748cdbfc445396deb6d24908521701aaa80aa"
  ],[
    820201,
    "904278b4bd585e3055c092aada1e030fbdf69a0e"
  ],[
    613201,
    "3317ea0a272976a10ef6593e840f9ff2032affad"
  ],[
    1315315,
    "baede744122d4b8d296ab3497bf5c849d1131466"
  ],[
    871001,
    "137ee1e9171a7ed1fe9cc58536d8e20749c3f199"
  ],[
    578901,
    "add6131c7bc6f1c9470de209b0e9c257d664f1c9"
  ],[
    494001,
    "59836f51f13e07be1de734a02360742c7b5f0dd6"
  ],[
    451501,
    "42e519db48f09570fcc02f38288648a92789dcb3"
  ],[
    554801,
    "4a992cc282a0024d393c6389cf84cbb8df1fc839"
  ],[
    408751,
    "12481e818abe9bc86069e45586df11d2cff7dbb8"
  ],[
    357001,
    "d240848ca9bf4be30204eded02fb35ce2e215d41"
  ],[
    340001,
    "d3858436100abe3ad7ee9f026e5f7f4781732e06"
  ],[
    1772201,
    "5832516564d86e86edbbb501cabec98c77504307"
  ],[
    316002,
    "206b7e6574019f4352515bd3d96162fb40a1b18a"
  ],[
    274001,
    "f46c109cfb1bac323122ae59b08edc23328d880c"
  ],[
    1575501,
    "52c5e5764fba4c876cde8c80e598c89ee5c35d9f"
  ],[
    1,
    "8abcfb93c52f999e3ef5288c4f837f4f15af5521"
  ]
]


[cube]

About 25% delegates are affected by it.  My delegate went into a folked chain.  Can the devs look into it?