[DBL] Doubloons: Pirate Currency

[Blazr2]

Is it not easier just put DBL patches into 0.9 LTC client?

That's what we'd like to do but we want to rectify the forking first. From some extensive fiddling with this last night here's where we stand:

The_Catman's client doesn't reliably want to synch past block 267269 on some machines. We think this is where the first fork started.

Explorer.doubloons.net is the authoritative chain at this point with 324072 (and climbing) blocks. This is the longer chain and should win-out.

Cryptsy hasn't responded to us about which block height they are at--but as mentioned we've already begun discussions with them about getting DBL fixed and they are receptive.

Here's what we're looking at doing:

The explorer's chain will be considered authoritative.

An updated DBL client which has correct checkpoints and additional seednodes will be released in the next day or two. This client will not be a hard fork (yet) and will be geared at getting everyone back in-synch with the new seednodes and explorer.

Once Cryptsy is updated to the newest code and back in-synch, we'll push out an updated-updated version of the client which will shut off the old nodes from connecting AND bring the code-base up to more recent standards.

Watch for the new client to be here in the next day or two!

[1714756303]

1714756303

[BitPhotos]

Is it not easier just put DBL patches into 0.9 LTC client?

That's what we'd like to do but we want to rectify the forking first. From some extensive fiddling with this last night here's where we stand:

The_Catman's client doesn't reliably want to synch past block 267269 on some machines. We think this is where the first fork started.

Explorer.doubloons.net is the authoritative chain at this point with 324072 (and climbing) blocks. This is the longer chain and should win-out.

Cryptsy hasn't responded to us about which block height they are at--but as mentioned we've already begun discussions with them about getting DBL fixed and they are receptive.

Here's what we're looking at doing:

The explorer's chain will be considered authoritative.

An updated DBL client which has correct checkpoints and additional seednodes will be released in the next day or two. This client will not be a hard fork (yet) and will be geared at getting everyone back in-synch with the new seednodes and explorer.

Once Cryptsy is updated to the newest code and back in-synch, we'll push out an updated-updated version of the client which will shut off the old nodes from connecting AND bring the code-base up to more recent standards.

Watch for the new client to be here in the next day or two!

this sounds great! glad to see this coin being revived!

[rav3n_pl]

Cool DBL always was my favorite scrypt coin, not want to see it gone in oblivion

[BitPhotos]

Cool DBL always was my favorite scrypt coin, not want to see it gone in oblivion

haha i could tell! btw just saw your signature, might want to change where it says skydrive to onedrive lol 

[Blazr2]

Here we have Doubloons v11 (Queen Anne's Revenge):



https://www.dropbox.com/s/s774sa1se9bzgiv/Doubloons-Qt-v11.rar

To ensure you're on the right chain, check with http://explorer.doubloons.net and verify block height once your client finishes synching. You may experience slow synching as there are a lot of blocks orphaned around 267200, if needs be, you can clear your %appdata%\Doubloons folder (but not your wallet.dat!) and resynch.

Adding this to your .conf may help as well:

Code:

banscore=1
addnode=explorer.doubloons.net
addnode=seed1.coinlab.info
addnode=seed2.coinlab.info
addnode=seed3.coinlab.info
addnode=seed4.coinlab.info

This can help synch the correct blocks and mirrors the seednodes internal to this new v11 client. Since shakezula's gone on to deeper waters, we have no way to update the main post, so pass this info around to your DBL compadres!

Cryptsy has been notified to upgrade and we anticipate they should be back on the correct chain in a few days time. Once transactions are flowing and blocks are happy again, we'll proceed to the next step of bringing the code up to more recent levels and possibly hard-forking for diff or coin-swapping to a new algo, but again, this a step in the right direction. We'll get DBL riding the high seas again!

[rav3n_pl]

Please link to git repo

[Blazr2]

Duh! https://github.com/thegreatoldone/doubloons

[rav3n_pl]

Ah, so only checkpoints... I was thinking about new code base...

[emece67]

...

Once transactions are flowing and blocks are happy again, we'll proceed to the next step of bringing the code up to more recent levels and possibly hard-forking for diff or coin-swapping to a new algo, but again, this a step in the right direction. We'll get DBL riding the high seas again!

Thanks a lot for your work. Now synching and hoping not all of my coins got lost.

Just in case the new algo question is open to debate, I'll propose to change to a less power demanding algorithm, such as Gröstl.

[Blazr2]

Ah, so only checkpoints... I was thinking about new code base...

Yes, it will happen but baby steps

[rav3n_pl]

Updated anyway, still mining on my GPU

[Petr1fied]

I've had no problem remaining fully in sync with http://explorer.doubloons.net for the last couple of weeks on Windows using 0.10.0.0 although the same was not true a few weeks ago. I think the issue was more due to a single dodgy peer contaminating things rather than anything else.

Nice to see further development though, DBL has always been one of my favorite coins and it's been sad to see it decline. Who doesn't enjoy saying Arrrrrrr! like a pirate?

Updated to 0.11.0.0

[ahmed_bodi]

mining away gracefully on the current FNU only pool

[skyrace]

What about exchange?

[Blazr2]

What about exchange?

As per reply from "Mullick" at Cryptsy from yesterday, its actively being worked on and shouldn't be much longer until its back in business. If you want to see DBL on other exchanges, that's up to the community.

[zveryock]

Update chain blocks was on May 17, how to solve the problem with the update?

[Petr1fied]

Update chain blocks was on May 17, how to solve the problem with the update?

What problem with the update? Just download the latest version, delete the contents of the %Appdata%\Doubloons folder (excluding wallet.dat) and redownload the blocks.

[Blazr2]

Cryptsy has given the greenlight that their DBL client is updated and back online. Will be doing some tests with it tonight/tomorrow and if all goes well, on to the next step!

[Petr1fied]

I've put my old Doubloons faucet and Block Crawler back online. If anyone needs a good list of peers check the sync help page.

[zveryock]

Update chain blocks stopped at block 267269, and all connections are down. That make that purse has been updated to the end?