working v12 https://github.com/Rav3nPL/doubloons-08
experimental v13 https://github.com/Rav3nPL/doubloons-0.10
older https://github.com/razorlove/doubloons - can not connect properly
All version have sync issues in first ~100k blocks, you need restart client when it stuck.
Topic: [DBL] Doubloons: Pirate Currency - page 7. (Read 139905 times)
and some working source code?
what will happend after touch 8M coins?
with the situation at cryptsy dbl could end up without being listed anywhere.
currently cryptopia has a cryptsy coin listing offer https://www.cryptopia.co.nz/Forum/Thread/492
just a thought
currently cryptopia has a cryptsy coin listing offer https://www.cryptopia.co.nz/Forum/Thread/492
just a thought
My node rav3n.dtdns.net is mostly running, you can easily setup own p2pool or solo 
v12, on 1008052 block stop:
where i can mine? pool? p2pool?
Code:
{
"blocks" : 1008052,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.41332139,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 10125087,
"pooledtx" : 2,
"testnet" : false
}
where i can mine? pool? p2pool?
Looks like v13 stuck on 1005625 and v12 (and earlier) on 1008052
Sadly I have no scrypt miner to put some hr and swing it.
Sadly I have no scrypt miner to put some hr and swing it.
i'm still on v12
blockchain stuck on "blocks" : 1008052
sadly i sent all of my dbl from cryptsy back to my wallet its been 2 days since and 0 confirmations
connected to
blockchain stuck on "blocks" : 1008052
Code:
{
"version" : 120000,
"protocolversion" : 80000,
"walletversion" : 60000,
"balance" : xxxx,
"blocks" : 1008052,
"timeoffset" : 0,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.41332139,
"testnet" : false,
"keypoololdest" : 1410813075,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}sadly i sent all of my dbl from cryptsy back to my wallet its been 2 days since and 0 confirmations
connected to
Code:
"addr" : "91.235.254.37:1336",
"addr" : "93.100.107.4:1336",
what about http://dbl.dtdns.net:8345 ? not responde
Ok, looks like we have a problem.
My newest ("whydah") version based on 0.10.2 LTC has been widely used for mining, and v3 blocks fork kicks in.
This version is not accepting v2 blocks any more!
There is probably some major network fork, where v12 ("newprovidence", "queens annie revenge") and earlier miners are still mining (LTC versions 0.8 and older, v2 blocks), but newest clients not want to accept theirs blocks.
I`m now starting older version of daemon on my node to see where it goes and will compare what block see "whydah" and where is "newprovidence".
My "newprovidence" windows is on block 1005625 78f08433a1d4ba604356ecd8a7c25fd948c09d3cfa1a97bd48cec0db96544cb9 and showing "2 days behind".
edit:
My "whydah" is in same place, log shows:
edit2:
Found node that is still mining v2 blocks (or is connected to one that is mining):
edit3:
My windoze v12 node is synced up to 1006406 bf311a20f9c704c30256b17867c44a7468e40ac31704ec1e9cedc1c882656aea and showing up "Warning: This version is obsolete, upgrade required!" and counting
My linux v12 node still syncing (830xxx atm)...
Linux v13 stopped on 1005625.
Looks like v13 need moar tuning to adapt to longer chain and finally fix sync issues in first few hundred thousand blocks.
Miners, pls NOT mine on v13 "wyhdah" any more! When my node sync it will be v12 until v13 is finished.
Also, when we launch mining on v13, versions prior v12 will not connect to network (v13 need nodes that have "get headers" message, older clients not have it) and mining will be possible ONLY on v13 (because of v3 block version)!
So, if you are using ANY version under v12 upgrade NOW!
My newest ("whydah") version based on 0.10.2 LTC has been widely used for mining, and v3 blocks fork kicks in.
This version is not accepting v2 blocks any more!
There is probably some major network fork, where v12 ("newprovidence", "queens annie revenge") and earlier miners are still mining (LTC versions 0.8 and older, v2 blocks), but newest clients not want to accept theirs blocks.
I`m now starting older version of daemon on my node to see where it goes and will compare what block see "whydah" and where is "newprovidence".
My "newprovidence" windows is on block 1005625 78f08433a1d4ba604356ecd8a7c25fd948c09d3cfa1a97bd48cec0db96544cb9 and showing "2 days behind".
edit:
My "whydah" is in same place, log shows:
Code:
2015-12-16 08:30:01 ERROR: ContextualCheckBlockHeader : rejected nVersion=2 block
2015-12-16 08:30:01 ERROR: invalid header received
2015-12-16 08:30:01 ProcessMessage(headers, 16039 bytes) FAILED peer=10
2015-12-16 08:30:01 ERROR: ContextualCheckBlockHeader : rejected nVersion=2 block
2015-12-16 08:30:01 ERROR: invalid header received
2015-12-16 08:30:01 ProcessMessage(headers, 16039 bytes) FAILED peer=1
2015-12-16 08:30:01 ERROR: ContextualCheckBlockHeader : rejected nVersion=2 block
2015-12-16 08:30:01 ERROR: invalid header received
2015-12-16 08:30:01 ProcessMessage(headers, 16039 bytes) FAILED peer=7
edit2:
Found node that is still mining v2 blocks (or is connected to one that is mining):
Code:
receive version message: /Satoshi:0.12.0/: version 80000, blocks=1006075, us=91.235.254.37:53998, peer=12, peeraddr=93.100.107.4:1336
2015-12-16 12:34:47 connect() to 70.163.93.56:1336 failed after select(): Connection refused (111)
2015-12-16 12:36:23 ERROR: ContextualCheckBlockHeader : rejected nVersion=2 block
2015-12-16 12:36:23 ERROR: invalid header received
2015-12-16 12:36:23 ProcessMessage(headers, 36534 bytes) FAILED peer=12
2015-12-16 12:37:00 ERROR: ContextualCheckBlockHeader : rejected nVersion=2 block
2015-12-16 12:37:00 ERROR: invalid header received
edit3:
My windoze v12 node is synced up to 1006406 bf311a20f9c704c30256b17867c44a7468e40ac31704ec1e9cedc1c882656aea and showing up "Warning: This version is obsolete, upgrade required!" and counting
My linux v12 node still syncing (830xxx atm)...
Linux v13 stopped on 1005625.
Looks like v13 need moar tuning to adapt to longer chain and finally fix sync issues in first few hundred thousand blocks.
Miners, pls NOT mine on v13 "wyhdah" any more! When my node sync it will be v12 until v13 is finished.
Also, when we launch mining on v13, versions prior v12 will not connect to network (v13 need nodes that have "get headers" message, older clients not have it) and mining will be possible ONLY on v13 (because of v3 block version)!
So, if you are using ANY version under v12 upgrade NOW!
last block 1005625 Mon, 14 Dec 2015 06:24:31 GMT
network is dead?
network is dead?
Maybe use some fresh version of wallet?
I`m restarting my home node, but it may not be 24/7 :/
rav3n.dtdns.net:8345
dbl.dtdns.net is down, need some cash to pay for VPS.
I`m restarting my home node, but it may not be 24/7 :/
rav3n.dtdns.net:8345
dbl.dtdns.net is down, need some cash to pay for VPS.
disk C: - 25GB free
disk D: - 40Gb free
wallet on disk C
p.s: http://dbl.dtdns.net:8345/static/ is alive?
p.s.s: what this in debag.log ?
....
accepted connection 204.11.237.233:32796
send version message: version 70000, blocks=1005212, us=93.100.107.4:1336, them=204.11.237.233:32796, peer=204.11.237.233:32796
receive version message: version 80000, blocks=1005212, us=93.100.107.4:1336, them=204.11.237.233:11138, peer=204.11.237.233:32796
getblocks -1 to 00000000000000000000 limit 500
IRC :irc.smutfairy.com NOTICE * :*** Looking up your hostname
IRC :irc.smutfairy.com NOTICE * :*** Couldn't look up your hostname
IRC SENDING: NICK u6FKjFa836jLcrL
IRC SENDING: USER u6FKjFa836jLcrL 8 * : u6FKjFa836jLcrL
IRC :irc.smutfairy.com 433 * u6FKjFa836jLcrL :Nickname is already in use.
IRC name already in use
IRC waiting 10 seconds to reconnect
trying connection 192.95.29.214:1336 lastseen=27.0hrs
connection timeout
trying connection 91.235.254.37:1336 lastseen=375029.7hrs
connection timeout
connection timeout
trying connection 91.235.254.37:1336 lastseen=375029.7hrs
trying connection 192.95.29.214:1336 lastseen=27.0hrs
IRC :irc.smutfairy.com NOTICE * :*** Looking up your hostname
IRC :irc.smutfairy.com NOTICE * :*** Couldn't look up your hostname
IRC SENDING: NICK u6FKjFa836jLcrL
IRC SENDING: USER u6FKjFa836jLcrL 8 * : u6FKjFa836jLcrL
IRC :irc.smutfairy.com 433 * u6FKjFa836jLcrL :Nickname is already in use.
IRC name already in use
IRC waiting 10 seconds to reconnect
connection timeout
connection timeout
......
disk D: - 40Gb free
wallet on disk C
p.s: http://dbl.dtdns.net:8345/static/ is alive?
p.s.s: what this in debag.log ?
....
accepted connection 204.11.237.233:32796
send version message: version 70000, blocks=1005212, us=93.100.107.4:1336, them=204.11.237.233:32796, peer=204.11.237.233:32796
receive version message: version 80000, blocks=1005212, us=93.100.107.4:1336, them=204.11.237.233:11138, peer=204.11.237.233:32796
getblocks -1 to 00000000000000000000 limit 500
IRC :irc.smutfairy.com NOTICE * :*** Looking up your hostname
IRC :irc.smutfairy.com NOTICE * :*** Couldn't look up your hostname
IRC SENDING: NICK u6FKjFa836jLcrL
IRC SENDING: USER u6FKjFa836jLcrL 8 * : u6FKjFa836jLcrL
IRC :irc.smutfairy.com 433 * u6FKjFa836jLcrL :Nickname is already in use.
IRC name already in use
IRC waiting 10 seconds to reconnect
trying connection 192.95.29.214:1336 lastseen=27.0hrs
connection timeout
trying connection 91.235.254.37:1336 lastseen=375029.7hrs
connection timeout
connection timeout
trying connection 91.235.254.37:1336 lastseen=375029.7hrs
trying connection 192.95.29.214:1336 lastseen=27.0hrs
IRC :irc.smutfairy.com NOTICE * :*** Looking up your hostname
IRC :irc.smutfairy.com NOTICE * :*** Couldn't look up your hostname
IRC SENDING: NICK u6FKjFa836jLcrL
IRC SENDING: USER u6FKjFa836jLcrL 8 * : u6FKjFa836jLcrL
IRC :irc.smutfairy.com 433 * u6FKjFa836jLcrL :Nickname is already in use.
IRC name already in use
IRC waiting 10 seconds to reconnect
connection timeout
connection timeout
......
Is says that you have no space on disk... see in debug.log
{
"blocks" : 1005215,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.16553966,
"errors" : "EXCEPTION: 11DbException \nDb::put: Not enough space \nD:\\doubloons-qt-0.10.0.0\\doubloons-qt.exe in ProcessMessages() \n",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1254573,
"pooledtx" : 0,
"testnet" : false
}
what is this error ?
"blocks" : 1005215,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.16553966,
"errors" : "EXCEPTION: 11DbException \nDb::put: Not enough space \nD:\\doubloons-qt-0.10.0.0\\doubloons-qt.exe in ProcessMessages() \n",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1254573,
"pooledtx" : 0,
"testnet" : false
}
what is this error ?
"blocks" : 1000132, on my v12 windows client, 2 connections in few sec.
why not sync?
wallet v12, 6 connection to network
wallet v12, 6 connection to network
LOutCh@nO MultiPool
New Doubloons Pool Yarrr! 1% fee
Pool : http://multipool.no-ip.org:2627/pool/DBL/
Facebook : https://www.facebook.com/loutchanomultipool/
Twitter : https://twitter.com/LOutChanoPool
Contact : [email protected]
Donations DBL : ArNkRE4udSgwUAusPyS51M8FukxDt4G5Bp
Happy Mining !!!
New Doubloons Pool Yarrr! 1% fee
Pool : http://multipool.no-ip.org:2627/pool/DBL/
Facebook : https://www.facebook.com/loutchanomultipool/
Twitter : https://twitter.com/LOutChanoPool
Contact : [email protected]
Donations DBL : ArNkRE4udSgwUAusPyS51M8FukxDt4G5Bp
Happy Mining !!!
Jump to: