[DBL] Doubloons: Pirate Currency

[Petr1fied]

I actually spoke to Mullick about it in real time several weeks ago and he stated "I'm on it".

The truth is cryptsy only cares about their high volume coins because those are what generate their fees. If a coin falls by the wayside and hasn't had significant trading for months then they really couldn't care less about resolving the problem, even if it would take a couple of hours of their time at most to update their client and resync.

Cryptsy don't really care about their customers and opening a ticket is pointless if you want anything other than a copy & paste response. That is one of the reasons Cryptsy has lost it's market position and people are migrating to other exchanges en-mass.

[Blazr2]

Your patience has been rewarded:



DBL's are up and running again on Cryptsy. Now on to part two, bringing the DBL client in to the future. No hardforks, no coin swaps, just fresh clean code coming soon.

[Petr1fied]

Glad to see Cryptsy have finally gotten their act together.

[kelsey]

DBL's are up and running again on Cryptsy. Now on to part two, bringing the DBL client in to the future. No hardforks, no coin swaps, just fresh clean code coming soon.

though being pirate currency...proof of stake would kinda make sense 

[faraway]

Doubloons is another Great Alternate.

[rav3n_pl]

DBL code to litecoin 0.8 work in progress: https://github.com/Rav3nPL/doubloons-08
YaRRr!

[rav3n_pl]

Looks like daemon IS working!
Any participants to change logos etc? I not have experience on this side ;]

[Harryredkon]

Where can i mine it ?

[rav3n_pl]

If not solo, my P2pool node http://rav3n.dtdns.net:8345/ and some Russian node http://195.130.216.149:8345

[mullick]

Glad to see Cryptsy have finally gotten their act together.

It was not a matter of us getting our act together.

I had posted MULTIPLE times in this thread about the issue and i was not the only one experiencing it.

I tried about a dozen times over a 3 week period to get DBL back up and running. Every single time it would drop peers within an hour of syncing. Again after the update tried 3 times over 3 days still nothing

Whatever the problem was it appears to have been resolved as we are now keeping peers

Im pretty shocked at all of the "Cryptsy doesnt care" talk in this thread. If we didnt I wouldnt have tried as much as I did with a coin that obviously was having blockchain issues. It was suspended due to an issue with the network. We were NOT the only ones having the issue. Hence why the update was released

The only way to back on track is delete blockchain and download it again.
When forked, daemon cant go back in track. Have no idea why.

My connections:

Code:

addnode=46.4.98.205
addnode=70.98.114.237
addnode=128.199.204.144
addnode=71.162.169.212
addnode=138.100.48.9
addnode=192.99.44.51
addnode=62.84.249.76
addnode=99.248.212.33
addnode=71.162.169.212
addnode=188.226.239.106
addnode=188.81.86.33
addnode=74.57.153.8
addnode=95.166.151.96
addnode=95.69.228.171
addnode=91.235.254.37

I have redownloaded, Rebuilt and rescanned 7 out of the last 10 days. Only to find it with 0 peers and behind the network the very next day each time. Im working on it and will let you know when Its resolved

The wallet is not staking via reservebalance=9999999

I havent given up yet. Still have a few things im going to try

Code:

received block 91e9f191971019c02bd9
ProcessBlock: ORPHAN BLOCK, prev=a7b8624ae0fdb17f6a23
received block d0de08546119c83a85f7
  nActualTimespan = 1867  before bounds
GetNextWorkRequired RETARGET
nTargetTimespan = 1800    nActualTimespan = 1867
Before: 1d02ff07  00000002ff070000000000000000000000000000000000000000000000000000
After:  1d031b93  000000031b93eb17e4b17e4b17e4b17e4b17e4b17e4b17e4b17e4b17e4b17e4b
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 68.231.4.146:1336
Disconnected 68.231.4.146:1336 for misbehavior (score=100)

Still dropping peers.

Code:

addnode=217.24.189.155
addnode=70.98.114.237
addnode=70.98.114.229
addnode=91.235.254.37
maxconnections=4

I believe im banned by the good nodes

Code:

doubloons getpeerinfo
[
    {
        "addr" : "207.161.3.73:1336",
        "services" : "00000001",
        "lastsend" : 1400684403,
        "lastrecv" : 1400684404,
        "conntime" : 1400684403,
        "version" : 70000,
        "subver" : "/Satoshi:0.10.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 265169,
        "banscore" : 0
    },
    {
        "addr" : "98.116.101.140:1336",
        "services" : "00000001",
        "lastsend" : 1400684410,
        "lastrecv" : 1400684410,
        "conntime" : 1400684409,
        "version" : 70000,
        "subver" : "/Satoshi:0.10.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 266339,
        "banscore" : 0
    }
]

FYI This is the exact same problem we were having. And we did update. So despite what you said it is possible

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

Perhaps read the post right above your own? Here let me highlight the relevant section for you:

If anyone needs a good list of peers check the sync help page.

Follow all the instructions on that page and you should be fully synced within a few hours.

did everything as written and stopped on the block 267269

For you to lock up on that exact block every single time is impossible if you follow the instructions to the letter.

You need to use wallet v11

I concur, he's either trying to sync a very old version (earlier than 0.10.0.0) or he didn't delete the old blocks before trying to re-sync. Updating the client and deleting the old blocks are both covered in the directions.

[hf100]

Thanks for keeping it alive on Cryptsy mullick.

[Blazr2]

Yes, thank you Mullick and Cryptsy.

[rav3n_pl]

It was not a matter of us getting our act together.

I had posted MULTIPLE times in this thread about the issue and i was not the only one experiencing it.

I tried about a dozen times over a 3 week period to get DBL back up and running. Every single time it would drop peers within an hour of syncing. Again after the update tried 3 times over 3 days still nothing

Trouble with syncing is because of way that block are send by peers, sometimes one peer send "later" blocks that are after next diff change, and when it is lower than "current" it is marked as "misbehaving" node and it is dropped. Nothing bad is happening on sending node side, you need to restart own node to clear bans you have.

At some point, I made simple script that allow me to sync:

Code:

#!/bin/bash
while true
do
doubloons
sleep 10m
doubloons stop
sleep 10s
done

It is restarting daemon every 10 minutes, you just need check after 2-3 hours that it is synced and run it in normal way.
Also adding

Code:

timeout=500

to doubloons.conf file can help a bit to find nodes faster. But it also dropping "slow" nodes...

All the troubles are because we have too small number of nodes...

[beitris.dwlul]

 I bet we can up that bounty even further perhaps too if there's interest.

[Blazr2]

Looks like daemon IS working!
Any participants to change logos etc? I not have experience on this side ;]

If you don't mind, we'll change the logos and make some new wallets from your source, we've simply had no time to get back to this one yet despite offering the help!

[alt19]

Have a good day everyone!

It's very good this coin is being revived.
The idea I've posted here https://bitcointalk.org/index.php?topic=655461.0
that old, memorable coins of pretty small capitalisation, but with bright names and dramatic trade history have great advantages.

Doubloons are included in ALT100 Market Index and in ALT_Collectibles Index.
http://alt19.com

[rav3n_pl]

Looks like daemon IS working!
Any participants to change logos etc? I not have experience on this side ;]

If you don't mind, we'll change the logos and make some new wallets from your source, we've simply had no time to get back to this one yet despite offering the help!

Sure, all on git Just make PR.
One of my mate on another forum do this, but something is messed in his git and can`t merge...
My repo: https://github.com/Rav3nPL/doubloons-08
Kot`s fork: https://github.com/9kot9/doubloons

[kelsey]

any revive happening on this, another coin that would be a pity to let die?

[Spoetnik]

any revive happening on this, another coin that would be a pity to let die?

"let" ?

i think we past that long ago kelsey lol

[kelsey]

any revive happening on this, another coin that would be a pity to let die?

"let" ?

i think we past that long ago kelsey lol

hey why I still own some its not dead
honestly named too