Topic: Bottlecaps Forked Chain Mandatory Update V 1.4 (Read 1176 times)
updated and block chain almost resynced!
Thank you for your prompt response. We're looking forward to the 1.4.1, hope it's not too far off! 
Downloads:
Source: https://docs.google.com/file/d/0B0V-7FME2rcyZUNPTkJSQ3hVd2M/edit?usp=sharing
Windows-Qt: https://docs.google.com/file/d/0B0V-7FME2rcyT3NmNXRiWU11Rm8/edit?usp=sharing CTRL+S or go to File then download to download the .rar. Files cannot be downloaded individually. That is the source of the confusion with the 404 errors
Version 1.4 Release notes. We worked furiously through out the day to nail down the location of the forks. We got the necessary checkpoints and changes in place to get synced to the longest chain. At the time of this release it had a block height of 50610. It was the chain Multipool and verns pool have been on. We have added more dedicated nodes and will include even more in the upcoming release. Now appointed 1.4.1 This release has been only slightly delayed to ensure the network regains full functionality and security.
Once cryptsy resumes trading and is on the correct chain all deposits should begin to go through if the sender has updated to the new client. As long as the coins were not minted on the incorrect chain. Erundooks pool seems to be the most affected by this decision. We are sincerely sorry for any loss to the miners at his or any other pool that was affected.
We decided to go with this chain to reduce the overall loss to the miners. They were in no way at fault for this and we hope this minimizes losses as much as possible. The majority of the network was also on this chain
I struggled to narrow down th correct chain due to the explorers them selves being out of sync. I had a immense amount of help from Justin7674. I would not have been able to narrow down the forks and get the client syncing correctly without him. Bottlecaps development is a very unrewarding position. We appreciate his help very much
Installation instructions Windows QT:
1. Close your client and delete the folder that contains Bottlecaps V1.3
2. Click Start and search Run.
3. Run the location %appdata%
4. Navigate to roaming/Bottlecaps
5. Delete everything in this folder accept Wallet.dat and Bottlecaps.conf
6. In your Bottlecaps.conf folder remove all nodes and add the following
addnode=192.241.148.204
addnode=199.180.115.100
addnode=199.180.115.125
6. Extract the new Bottlecaps V1.4 folder to your desired location
7. Run Bottlecaps-qt.exe and patiently wait for the correct blockchain to download
We will have a full briefing on any and all losses incurred by this unfortunate situation within the next 24 hours. For now Get back to mining!
Source: https://docs.google.com/file/d/0B0V-7FME2rcyZUNPTkJSQ3hVd2M/edit?usp=sharing
Windows-Qt: https://docs.google.com/file/d/0B0V-7FME2rcyT3NmNXRiWU11Rm8/edit?usp=sharing CTRL+S or go to File then download to download the .rar. Files cannot be downloaded individually. That is the source of the confusion with the 404 errors
Version 1.4 Release notes. We worked furiously through out the day to nail down the location of the forks. We got the necessary checkpoints and changes in place to get synced to the longest chain. At the time of this release it had a block height of 50610. It was the chain Multipool and verns pool have been on. We have added more dedicated nodes and will include even more in the upcoming release. Now appointed 1.4.1 This release has been only slightly delayed to ensure the network regains full functionality and security.
Once cryptsy resumes trading and is on the correct chain all deposits should begin to go through if the sender has updated to the new client. As long as the coins were not minted on the incorrect chain. Erundooks pool seems to be the most affected by this decision. We are sincerely sorry for any loss to the miners at his or any other pool that was affected.
We decided to go with this chain to reduce the overall loss to the miners. They were in no way at fault for this and we hope this minimizes losses as much as possible. The majority of the network was also on this chain
I struggled to narrow down th correct chain due to the explorers them selves being out of sync. I had a immense amount of help from Justin7674. I would not have been able to narrow down the forks and get the client syncing correctly without him. Bottlecaps development is a very unrewarding position. We appreciate his help very much
Installation instructions Windows QT:
1. Close your client and delete the folder that contains Bottlecaps V1.3
2. Click Start and search Run.
3. Run the location %appdata%
4. Navigate to roaming/Bottlecaps
5. Delete everything in this folder accept Wallet.dat and Bottlecaps.conf
6. In your Bottlecaps.conf folder remove all nodes and add the following
addnode=192.241.148.204
addnode=199.180.115.100
addnode=199.180.115.125
6. Extract the new Bottlecaps V1.4 folder to your desired location
7. Run Bottlecaps-qt.exe and patiently wait for the correct blockchain to download
We will have a full briefing on any and all losses incurred by this unfortunate situation within the next 24 hours. For now Get back to mining!
Jump to: