[DBL] Doubloons: Pirate Currency

[rav3n_pl]

My node:

Code:

 doubloons getinfo
{
    "version" : 120000,
    "protocolversion" : 80000,
    "walletversion" : 60000,
-
    "blocks" : 721371,
    "timeoffset" : -1,
    "connections" : 16,
    "proxy" : "",
    "difficulty" : 1.09385432,

Have no idea why explorer is locked on 716816...

[1714877520]

1714877520

[1714877520]

1714877520

[1714877520]

1714877520

[1714877520]

1714877520

[1714877520]

1714877520

[mullick]

Whats going on with the chain?

Tried a few times to get our wallet synced again. On this last attempt

REORGANIZE: Disconnect 2892 blocks; d2fb7f0c06f8f89a7ede..7c6965441b0a1ee207f4
REORGANIZE: Connect 3825 blocks; d2fb7f0c06f8f89a7ede..33401386e87b1fdea18c

Quite a few unconfirmed transactions because of this. Looks like the wallet was down when these hit so they never made it to accounts thankfully

EDIT: Bah now im getting these. Ill sync from scratch again

Code:

************************
EXCEPTION: 11DbException       
Db::put: Cannot allocate memory       
doubloons in ProcessMessages()       



************************
EXCEPTION: 11DbException       
Db::put: Cannot allocate memory       
doubloons in ProcessMessages() 

[rav3n_pl]

Use bootstrap from my onedrive and sync on rest on network (link under post).
I`m working on fork v0.10 LTC to work on DBL, all fork and sync issues should be gone.

[mullick]

Use bootstrap from my onedrive and sync on rest on network (link under post).
I`m working on fork v0.10 LTC to work on DBL, all fork and sync issues should be gone.

Ill try to get it up tomorrow. I dont use 3rd party bootstraps in production so will have to import it from another server.

If the wallet bans other peers or gets another large reorganization i cant guarantee it will stay up long though

[rav3n_pl]

Its ok, it should work this way. Just do -reindex when copy block data.
My node is on chain:

Code:

 doubloons getinfo
{
    "version" : 120000,
    "protocolversion" : 80000,
    "walletversion" : 60000,

    "blocks" : 747581,
    "timeoffset" : 1,
    "connections" : 15,
    "proxy" : "",
    "difficulty" : 0.53494466,

My outgoing connections:

Code:

addnode=5.166.182.75
addnode=134.249.144.169
addnode=192.99.37.133

I have 1 connection to v10 (out), 1 to v11 (in), rest is to v12.

[rav3n_pl]

Uploading new linear 7zipped boostrap.dat file and peers.dat into my OneDrive.
MD5 of archive:

Code:

7c60c27042447336b8af3dd8af45cfbb *dbl_bootstrap_748000_13-05-2015.7z

Included info.txt:

Doubloons [DBL] bootstrap file and peers data as of 13-05-2015 up to block

getblockhash 748000
3e87d89c89bd20cf8b7ed5d02ff80446fa9c18731f5bab1ff245cb4abcabb86d

MD5
17db76013c8cfedf4b1e1a3072903b85 *bootstrap.dat
d2352d248c38948dbcd5a0ebed2c37bd *peers.dat

rav3n_pl

[kelsey]

interest trading wise seems to have built last few days   

[kelsey]

and tbh i'd be half tempted to sell if it wasn't for the fact it took me so long (due to lack of sellers) to acquire the amount i have, also i get a sense by the bigger buy walls that somethings up.

so any news?

[rav3n_pl]

Some peers that are on "right" chain (751k+ blocks).

Code:

195.177.74.50:1338
192.99.37.133:1336
81.195.148.82:1336
93.100.107.4:1336
91.237.77.7:1336
86.186.165.241:1337
192.99.2.213:1336
92.37.154.109:1336
189.33.133.252:1336
91.235.254.37:1336

There is some old v10 node that stuck on 200k+ blocks for days on 204.11.237.233 and try to connect over and over, I`d recommend to ban this IP for now.

[mullick]

There is some old v10 node that stuck on 200k+ blocks for days on 204.11.237.233 and try to connect over and over, I`d recommend to ban this IP for now.

Thats one of my old servers for altexplorer. Ill shut it down tonight

[acckill]

anyone know when the cryptsy wallet will be out of maintenance mode

[rav3n_pl]

Looks like thy have some connection to one of frozen block explorers.
Currently synced nodes ("blocks" : 788484, "difficulty" : 2.79734934,):

addnode=192.99.37.133:1336
addnode=91.237.77.7:1336
addnode=192.99.2.213:1336
addnode=194.44.203.196:1336
addnode=88.106.46.164:1336
addnode=46.151.21.226:1336
addnode=62.68.156.214:1336
addnode=91.235.254.37:1336

[hexdump]

Whats going on with the chain?

Tried a few times to get our wallet synced again. On this last attempt

REORGANIZE: Disconnect 2892 blocks; d2fb7f0c06f8f89a7ede..7c6965441b0a1ee207f4
REORGANIZE: Connect 3825 blocks; d2fb7f0c06f8f89a7ede..33401386e87b1fdea18c

Quite a few unconfirmed transactions because of this. Looks like the wallet was down when these hit so they never made it to accounts thankfully

EDIT: Bah now im getting these. Ill sync from scratch again

Code:

************************
EXCEPTION: 11DbException       
Db::put: Cannot allocate memory       
doubloons in ProcessMessages()       



************************
EXCEPTION: 11DbException       
Db::put: Cannot allocate memory       
doubloons in ProcessMessages() 

i used to  have the same problem it happened on random basis
I upgraded my wallet to "version" : 120000 and its been stable since then

[acckill]

i got 7800 doubloons for sale send me a pm if interested

[TrinityCoin]

i got 7800 doubloons for sale send me a pm if interested

Ill buy them.. 1 liteoshi each

[hexdump]

any update from cryptsy ?
new wallet is  stable like a rock

[navist]

i got 10 000 doubloons for sale

[rav3n_pl]

I`m still working on DBL v13 based on 0.10 LTC.
https://github.com/Rav3nPL/doubloons-0.10
Current status:
+ daemon working and syncing
- strings not replaced
- gui not done

When it will be ready, versions under 11 can not connect to new nodes. It is because of "getheaders" required by 0.10 Core.
Also, when BIP066 will kick in, all daemons prior 12 (based on Core 0. can produce invalid transactions.
Also, when BIP066 kick in, only this version will produce valid (v3) blocks!

So, get ready to upgrade!

Code:

./doubloons-cli getinfo
{
    "version" : 100202,
    "protocolversion" : 70003,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 836678,
    "timeoffset" : 0,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 1.32241661,
    "testnet" : false,
    "keypoololdest" : 1410856670,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00100000,
    "errors" : ""
}

[hexdump]

I`m still working on DBL v13 based on 0.10 LTC.
https://github.com/Rav3nPL/doubloons-0.10
Current status:
+ daemon working and syncing
- strings not replaced
- gui not done

When it will be ready, versions under 11 can not connect to new nodes. It is because of "getheaders" required by 0.10 Core.
Also, when BIP066 will kick in, all daemons prior 12 (based on Core 0. can produce invalid transactions.
Also, when BIP066 kick in, only this version will produce valid (v3) blocks!

So, get ready to upgrade!

Code:

./doubloons-cli getinfo
{
    "version" : 100202,
    "protocolversion" : 70003,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 836678,
    "timeoffset" : 0,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 1.32241661,
    "testnet" : false,
    "keypoololdest" : 1410856670,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00100000,
    "errors" : ""
}

thats awesome !!

[socoban]

I`m still working on DBL v13 based on 0.10 LTC.
https://github.com/Rav3nPL/doubloons-0.10
Current status:
+ daemon working and syncing
- strings not replaced
- gui not done

When it will be ready, versions under 11 can not connect to new nodes. It is because of "getheaders" required by 0.10 Core.
Also, when BIP066 will kick in, all daemons prior 12 (based on Core 0. can produce invalid transactions.
Also, when BIP066 kick in, only this version will produce valid (v3) blocks!

So, get ready to upgrade!

Code:

./doubloons-cli getinfo
{
    "version" : 100202,
    "protocolversion" : 70003,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 836678,
    "timeoffset" : 0,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 1.32241661,
    "testnet" : false,
    "keypoololdest" : 1410856670,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00100000,
    "errors" : ""
}

Maybe it is time to buy more DBL. The problem is, I believe LTC will pump heavily. So the question is, will DBL pump faster than LTC?