[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[tseug]

Is there a proper solution to get the wallet to sync past block 34139?

I started with no user data and a freshly compiled wallet from newest github revision, the nodes from 10-20 pages back and still no full sync. Tried without those nodes, again no user data, and same issue.

Any help?

[sippsnapp]

Is there a proper solution to get the wallet to sync past block 34139?

I started with no user data and a freshly compiled wallet from newest github revision, the nodes from 10-20 pages back and still no full sync. Tried without those nodes, again no user data, and same issue.

Any help?

I just compiled a new node list, not complete yet. Its p2p pool nodes and random connected nodes to my other nodes, all those nodes are pretty much 24/7 currently.
try at your own risk

http://pastebin.com/ERfv92JF

i just loaded a fresh compiled qt wallet wit hthese nodes in 3 minutes

Code:

23:08:26

getinfo


23:08:26

{
"version" : 90000,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : lolthastmylilsecret,
"blocks" : 35920,
"timeoffset" : 0,
"connections" : 31,
"proxy" : "",
"difficulty" : 217.37163291,
"testnet" : false,
"keypoololdest" : 1393894916,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}

[eduffield]

Some users have been asking me questions about what happened with the pool and KGW exploit. They were confused that the two were somehow connected and I thought I would clear it up.

Pool Exploit

The pool exploit was due to a miss-configuration of the stratum mining software that allowed miners to submit lower than normal difficulty shares. These shares were technically worthless and should have been invalid, but the software couldn't tell. If you're pool is still affected by this, here is how to fix it.  

Use the branch "Feature(MultiAlgo)" from this repo: https://github.com/Crypto-Expert/stratum-mining

After cloning that and checking out the correct branch, modify algo/coindefinition.py to use xcoin_hash.

Here's an example configuration for Darkcoin: http://paste.ubuntu.com/7116297/

KimotoGravityWell vs DarkGravityWave

We recently experienced a spike of difficulty from 300 to 10048 for one block. This was done by using a timewarp exploit on KimotoGravityWell where the user would submit an invalid timestamp on a block. To fix this issue without causing any unintended issues I implemented my own difficulty algorithm called DarkGravityWave, which uses 2 Exponential Moving Averages and 1 Simple Moving Average. These respond very quickly to shifts in the hashrate, but when invalid timestamps appear they can't impact the difficulty like we experienced before.

[eduffield]

Something stinks on Coindesk! I have been trying to submit the DEVs whitepaper on coindesk in the comments section, but for some reason they wont allow it??? Preferouss has 10 negative comments and I cant even submit one comment that shows what a turd he is??? Am I missing something?

I submitted a reply to that guy with all of the crazy comments, including the whitepaper and they deleted it too. I'm going to try just replying, maybe it's the link

[sippsnapp]

Some users have been asking me questions about what happened with the pool and KGW exploit. They were confused that the two were somehow connected and I thought I would clear it up.

Pool Exploit

The pool exploit was due to a miss-configuration of the stratum mining software that allowed miners to submit lower than normal difficulty shares. These shares were technically worthless and should have been invalid, but the software couldn't tell. If you're pool is still affected by this, here is how to fix it.  

Use the branch "Feature(MultiAlgo)" from this repo: https://github.com/Crypto-Expert/stratum-mining

After cloning that and checking out the correct branch, modify algo/coindefinition.py to use xcoin_hash.

Here's an example configuration for Darkcoin: http://paste.ubuntu.com/7116297/

KimotoGravityWell vs DarkGravityWave

We recently experienced a spike of difficulty from 300 to 10048 for one block. This was done by using a timewarp exploit on KimotoGravityWell where the user would submit an invalid timestamp on a block. To fix this issue without causing any unintended issues I implemented my own difficulty algorithm called DarkGravityWave, which uses 2 Exponential Moving Averages and 1 Simple Moving Average. These respond very quickly to shifts in the hashrate, but when invalid timestamps appear they can't impact the difficulty like we experienced before.

today i checked on that stratum darkcoin but how to execute that? i will need it in a few days for solomining rigs.

[chaeplin]

Ahhhh, I am so missing this as I needed to pick some up

@chaeplin

Moved my rig out. Thanks for the heads up.

^^ first page http://darckcoin.mine.nu/ (p2p) should changed to
                    http://darkcoin.mine.nu/ (p2pool node finder)

Yes typo (by me)

[coins101]

Something stinks on Coindesk! I have been trying to submit the DEVs whitepaper on coindesk in the comments section, but for some reason they wont allow it??? Preferouss has 10 negative comments and I cant even submit one comment that shows what a turd he is??? Am I missing something?

I submitted a reply to that guy with all of the crazy comments, including the whitepaper and they deleted it too. I'm going to try just replying, maybe it's the link

The journalist of the article has since been on twitter promoting darkcoin....looks like he tweeted your interview with Simone Brunozzi. Tweet him back the paper and ask for an interview /  write up on coindesk



https://twitter.com/jonmatonis

[chaeplin]

p2pool block found is anounced to irc.freenode.net #p2pool-drk

[child_harold]

Apparently we needed a white paper to be a legit crypto-currency, so here it is:

http://www.darkcoin.io/downloads/DarkcoinWhitepaper.pdf

Let me know if you see anything that could be improved, clearer, typos, etc.

Dark paper
(March 18, 2014)

[eduffield]

Something stinks on Coindesk! I have been trying to submit the DEVs whitepaper on coindesk in the comments section, but for some reason they wont allow it??? Preferouss has 10 negative comments and I cant even submit one comment that shows what a turd he is??? Am I missing something?

I submitted a reply to that guy with all of the crazy comments, including the whitepaper and they deleted it too. I'm going to try just replying, maybe it's the link

The journalist of the article has since been on twitter promoting darkcoin....looks like he tweeted your interview with Simone Brunozzi. Tweet him back the paper and ask for an interview /  write up on coindesk



https://twitter.com/jonmatonis

I would tweet him, but I've tried to post on coindesk to respond to preferrous and everything I write gets deleted. Why would they censor everything I say?

[tseug]

Is there a proper solution to get the wallet to sync past block 34139?

I started with no user data and a freshly compiled wallet from newest github revision, the nodes from 10-20 pages back and still no full sync. Tried without those nodes, again no user data, and same issue.

Any help?

I just compiled a new node list, not complete yet. Its p2p pool nodes and random connected nodes to my other nodes, all those nodes are pretty much 24/7 currently.
try at your own risk

http://pastebin.com/ERfv92JF

i just loaded a fresh compiled qt wallet wit hthese nodes in 3 minutes

Code:

23:08:26

getinfo


23:08:26

{
"version" : 90000,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : lolthastmylilsecret,
"blocks" : 35920,
"timeoffset" : 0,
"connections" : 31,
"proxy" : "",
"difficulty" : 217.37163291,
"testnet" : false,
"keypoololdest" : 1393894916,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}

Thanks but those nodes give me the same result for some reason (even after deleting the blockchain).

Could this be a build specific issue (this is a 32 bit linux build) maybe

[sippsnapp]

Is there a proper solution to get the wallet to sync past block 34139?

I started with no user data and a freshly compiled wallet from newest github revision, the nodes from 10-20 pages back and still no full sync. Tried without those nodes, again no user data, and same issue.

Any help?

I just compiled a new node list, not complete yet. Its p2p pool nodes and random connected nodes to my other nodes, all those nodes are pretty much 24/7 currently.
try at your own risk

http://pastebin.com/ERfv92JF

i just loaded a fresh compiled qt wallet wit hthese nodes in 3 minutes

Code:

23:08:26

getinfo


23:08:26

{
"version" : 90000,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : lolthastmylilsecret,
"blocks" : 35920,
"timeoffset" : 0,
"connections" : 31,
"proxy" : "",
"difficulty" : 217.37163291,
"testnet" : false,
"keypoololdest" : 1393894916,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}

Thanks but those nodes give me the same result for some reason (even after deleting the blockchain).

Could this be a build specific issue (this is a 32 bit linux build) maybe

im solely on x64 ubuntu , worked on 12.04 , 13.10 & 14.04

[coins101]

Something stinks on Coindesk! I have been trying to submit the DEVs whitepaper on coindesk in the comments section, but for some reason they wont allow it??? Preferouss has 10 negative comments and I cant even submit one comment that shows what a turd he is??? Am I missing something?

I submitted a reply to that guy with all of the crazy comments, including the whitepaper and they deleted it too. I'm going to try just replying, maybe it's the link

The journalist of the article has since been on twitter promoting darkcoin....looks like he tweeted your interview with Simone Brunozzi. Tweet him back the paper and ask for an interview /  write up on coindesk



https://twitter.com/jonmatonis

I would tweet him, but I've tried to post on coindesk to respond to preferrous and everything I write gets deleted. Why would they censor everything I say?

They have a moderation process for first time posts and adding links. If you email them they will manually check and respond: Keith Horwood: keith at coindesk dot com

[sippsnapp]

while checking my darkcoin-qt debug log i found these :

Code:

2014-03-18 23:02:44 CreateNewBlock(): total size 1000
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:44 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-03-18 23:02:58 AcceptToMemoryPool: 68.57.168.201:9999 /Satoshi:0.9.0/ : accepted 617038cb19e4f4fba215fd0d2f80f6962da93d8d4539228c4593d636c6aff48e (poolsz 1)
2014-03-18 23:03:00 AcceptToMemoryPool: 107.170.107.208:9999 /Satoshi:0.9.0/ : accepted dadcc1683fdf3aca71e720b015ea8a4fae364bbac70081e2afea3832a343d0d8 (poolsz 2)
2014-03-18 23:03:03 AcceptToMemoryPool: 66.172.33.187:9999 /Satoshi:0.9.0/ : accepted c34f46a2c39ab4947b2980c2676b5c04e5469e5c53d8d0da43b1c36aa2a339b7 (poolsz 3)
2014-03-18 23:03:05 AcceptToMemoryPool: 50.19.116.123:9999 /Satoshi:0.9.0/ : accepted 696de7f8d0fbf05eba04f399cd9cf1a17769deaca375e54132ffa4a4e6a44e0e (poolsz 4)
2014-03-18 23:03:08 AcceptToMemoryPool: 68.57.168.201:9999 /Satoshi:0.9.0/ : accepted 5af6b0dcce9dd9c1678fd23ec70d110b229594f10087d9d19830828966c8794d (poolsz 5)
2014-03-18 23:03:09 received getdata for: tx 5af6b0dcce9dd9c1678fd23ec70d110b229594f10087d9d19830828966c8794d
2014-03-18 23:03:09 AcceptToMemoryPool: 69.140.29.36:9999 /Satoshi:0.9.0/ : accepted 11e31eb58f6aa47d0c9f14b6ed30dd1e27488407e827564d9a32a5a6191e1e1b (poolsz 6)
2014-03-18 23:03:11 AcceptToMemoryPool: 77.8.239.177:9999 /Satoshi:0.9.0/ : accepted 0ebb116170fe7c49759cdb3ad74ab2a0069690bbe151976baa3ab322b005ec3e (poolsz 7)
2014-03-18 23:03:13 AcceptToMemoryPool: 69.140.29.36:9999 /Satoshi:0.9.0/ : accepted 0eb3ffa4bd7be6db42025c6d6dac59a8fc15413e21611398f79844422de25e2b (poolsz 8)
2014-03-18 23:03:31 AcceptToMemoryPool: 213.229.88.102:9999 /Satoshi:0.9.0/ : accepted 9053c1c1b752a46723970c85ce57a960cb6b9a50756eddddc3d2d9ec4b7b243c (poolsz 9)
2014-03-18 23:03:31 AcceptToMemoryPool: 81.151.165.89:9999 /Satoshi:0.9.0/ : accepted 355d07cd03887cd9813da8c0d973597e7dd486207b729e352705da36c2c8341d (poolsz 10)
2014-03-18 23:03:45 33
2014-03-18 23:03:45 CreateNewBlock(): total size 3408
2014-03-18 23:04:03 trying connection 23.21.204.34 lastseen=0,0hrs
2014-03-18 23:04:03 connected 23.21.204.34
2014-03-18 23:04:03 send version message: version 70002, blocks=35945, us=91.236.116.103:12908, them=23.21.204.34:9999, peer=23.21.204.34:9999
2014-03-18 23:04:04 socket closed
2014-03-18 23:04:04 disconnecting node 23.21.204.34
2014-03-18 23:04:04 AcceptToMemoryPool: 50.19.116.123:9999 /Satoshi:0.9.0/ : accepted c8399d5501a7f500fdb6cdca5e79dfd3e215a99db8ac6c8c9fdb46bf1f780218 (poolsz 11)
2014-03-18 23:04:04 AcceptToMemoryPool: 85.131.127.26:9999 /Satoshi:0.9.0/ : accepted 446326736662285a2f67c991981927cc1c08e9a82d5b27af751beab6dec176a3 (poolsz 12)
2014-03-18 23:04:05 received getdata for: tx c8399d5501a7f500fdb6cdca5e79dfd3e215a99db8ac6c8c9fdb46bf1f780218
2014-03-18 23:04:05 received getdata for: tx 446326736662285a2f67c991981927cc1c08e9a82d5b27af751beab6dec176a3
2014-03-18 23:04:08 trying connection 67.215.11.122 lastseen=0,0hrs
2014-03-18 23:04:08 connected 67.215.11.122
2014-03-18 23:04:08 send version message: version 70002, blocks=35945, us=91.236.116.103:12908, them=67.215.11.122:9999, peer=67.215.11.122:9999
2014-03-18 23:04:09 socket closed
2014-03-18 23:04:09 disconnecting node 67.215.11.122
2014-03-18 23:04:15 trying connection 23.21.204.34:9999 lastseen=359773,3hrs
2014-03-18 23:04:15 connected 23.21.204.34:9999
2014-03-18 23:04:15 send version message: version 70002, blocks=35945, us=91.236.116.103:12908, them=23.21.204.34:9999, peer=23.21.204.34:9999
2014-03-18 23:04:15 socket closed
2014-03-18 23:04:15 disconnecting node 23.21.204.34:9999
2014-03-18 23:04:16 trying connection 67.215.11.122:9999 lastseen=359773,3hrs
2014-03-18 23:04:16 connected 67.215.11.122:9999
2014-03-18 23:04:16 send version message: version 70002, blocks=35945, us=91.236.116.103:12908, them=67.215.11.122:9999, peer=67.215.11.122:9999
2014-03-18 23:04:16 socket closed
2014-03-18 23:04:16 disconnecting node 67.215.11.122:9999
2014-03-18 23:04:16 trying connection 54.248.227.151:9999 lastseen=359773,3hrs
2014-03-18 23:04:17 connected 54.248.227.151:9999
2014-03-18 23:04:17 send version message: version 70002, blocks=35945, us=91.236.116.103:12908, them=54.248.227.151:9999, peer=54.248.227.151:9999
2014-03-18 23:04:17 socket closed
2014-03-18 23:04:17 disconnecting node 54.248.227.151:9999

getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
what does this mean?

[eduffield]

Something stinks on Coindesk! I have been trying to submit the DEVs whitepaper on coindesk in the comments section, but for some reason they wont allow it??? Preferouss has 10 negative comments and I cant even submit one comment that shows what a turd he is??? Am I missing something?

I submitted a reply to that guy with all of the crazy comments, including the whitepaper and they deleted it too. I'm going to try just replying, maybe it's the link

The journalist of the article has since been on twitter promoting darkcoin....looks like he tweeted your interview with Simone Brunozzi. Tweet him back the paper and ask for an interview /  write up on coindesk



https://twitter.com/jonmatonis

I would tweet him, but I've tried to post on coindesk to respond to preferrous and everything I write gets deleted. Why would they censor everything I say?

They have a moderation process for first time posts and adding links. If you email them they will manually check and respond: Keith Horwood: keith at coindesk dot com

Thanks

[cshlock]

As the first anonymous coin, shouldn't the price be higher? It's getting frustrating seeing it so stagnant after I have continually sunk so much money into it. At first glance it looks like price manipulation, but I could be wrong. Anyone else want to chime in on this?

[sippsnapp]

As the first anonymous coin, shouldn't the price be higher? It's getting frustrating seeing it so stagnant after I have continually sunk so much money into it. At first glance it looks like price manipulation, but I could be wrong. Anyone else want to chime in on this?

rome wasnt built in a day

[humanitee]

As the first anonymous coin, shouldn't the price be higher? It's getting frustrating seeing it so stagnant after I have continually sunk so much money into it. At first glance it looks like price manipulation, but I could be wrong. Anyone else want to chime in on this?

1) It's in beta.
2) Due to (1) there is little marketing going on.
3) Super early adopters made huge gains and are no doubt locking some profits.

[coins101]

As the first anonymous coin, shouldn't the price be higher? It's getting frustrating seeing it so stagnant after I have continually sunk so much money into it. At first glance it looks like price manipulation, but I could be wrong. Anyone else want to chime in on this?

1) It's in beta.
2) Due to (1) there is little marketing going on.
3) Super early adopters made huge gains and are no doubt locking some profits.

You have to get an informal nod of approval from the community elders before you are allowed permission to go to the moon.

[chaeplin]

while checking my darkcoin-qt debug log i found these :

getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
what does this mean?

connected peer want new block from you, which you anounced.