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

[darkproton]

and here is the donate bar if limlim or anyone else wants to setup drk donations. Hopefully this makes it easier to institute
https://github.com/gorgeousborg/DarkcoinTemplate-DonationBar

[Standhaft]

I think the 1 GH/s guy that was on Lotterymining is now on coinmine.

coincidence? I think not. Why does he not mine solo, what is this?

[dark-sailor]

Hi all

Is it possible to mine with cpu as well as 2 7970 as i have a 8x pile-driver sitting doing nothing. Would it put to much stress on my miner. Has any one tried mining with a pile-driver if so what speed would I expect.

Thanks

[anonymousxx1503]

Dat difficulty



only for a block though it seems.

[Alohaboy?!]

Dat difficulty



only for a block though it seems.

huge jump.. like crazy

[eduffield]

DarkSend Beta Version 3.5 (v8.9.7)

- Session ID's are now tied to the blockHeight, so they'll be much more stable. Some users were reporting stale DarkSend messages all of the time because they couldn't sync.

Documentation:
http://darkcoin.io/downloads/DarkSendv3.pdf
http://darkcoin.io/downloads/DarkSendDocumentation.pdf

Links:
Windows: http://darkcoin.io/downloads/beta/darkcoin-qt.exe
Ubuntu 64 qt: http://darkcoin.io/downloads/beta/darkcoin-qt
Ubuntu 64 daemon: http://darkcoin.io/downloads/beta/darkcoind

What's Next?
The next update is going to be a big one, it'll probably take me a week maybe.

Currently the network uses 1 master node, so it's a centralized implementation. I'm going to write some tamper proof logic to pick a random node from the network and elect it as the master. This is a neat implementation, because when you leave on your client it supports the network and you'll randomly receive fees when people try to attack DarkSend ( or turn off their clients in mid-transaction, lose their internet connection, etc ). We should see a really healthy amount of full nodes because of this, maybe even more than Bitcoin itself eventually.

[aNTi-Vlact]

DarkSend Beta Version 3.5 (v8.9.7)

- Session ID's are now tied to the blockHeight, so they'll be much more stable. Some users were reporting stale DarkSend messages all of the time because they couldn't sync.

Documentation:
http://darkcoin.io/downloads/DarkSendv3.pdf
http://darkcoin.io/downloads/DarkSendDocumentation.pdf

Links:
Windows: http://darkcoin.io/downloads/beta/darkcoin-qt.exe
Ubuntu 64 qt: http://darkcoin.io/downloads/beta/darkcoin-qt
Ubuntu 64 daemon: http://darkcoin.io/downloads/beta/darkcoind

What's Next?
The next update is going to be a big one, it'll probably take me a week maybe.

Currently the network uses 1 master node, so it's a centralized implementation. I'm going to write some tamper proof logic to pick a random node from the network and elect it as the master. This is a neat implementation, because when you leave on your client it supports the network and you'll randomly receive fees when people try to attack DarkSend ( or turn off their clients in mid-transaction, lose their internet connection, etc ). We should see a really healthy amount of full nodes because of this, maybe even more than Bitcoin itself eventually.

Awesome! Can't wait to try it after work!

[wonko86]

DarkSend Beta Version 3.5 (v8.9.7)

- Session ID's are now tied to the blockHeight, so they'll be much more stable. Some users were reporting stale DarkSend messages all of the time because they couldn't sync.

Documentation:
http://darkcoin.io/downloads/DarkSendv3.pdf
http://darkcoin.io/downloads/DarkSendDocumentation.pdf

Links:
Windows: http://darkcoin.io/downloads/beta/darkcoin-qt.exe
Ubuntu 64 qt: http://darkcoin.io/downloads/beta/darkcoin-qt
Ubuntu 64 daemon: http://darkcoin.io/downloads/beta/darkcoind

What's Next?
The next update is going to be a big one, it'll probably take me a week maybe.

Currently the network uses 1 master node, so it's a centralized implementation. I'm going to write some tamper proof logic to pick a random node from the network and elect it as the master. This is a neat implementation, because when you leave on your client it supports the network and you'll randomly receive fees when people try to attack DarkSend ( or turn off their clients in mid-transaction, lose their internet connection, etc ). We should see a really healthy amount of full nodes because of this, maybe even more than Bitcoin itself eventually.

Really nice work

[humanitee]

snip

Great stuff as usual Evan!

[tifozi]

Session_ID seems to be stuck at 1000. Any nodes to be added?

Edit: spoke too soon. Executed a successful DarkSend

[chaeplin]

Dat difficulty



only for a block though it seems.

Code:

NEWBL 03-13 04:52:10 32430 344.18513048                                         
NEWBL 03-13 04:52:48 32431 351.97650267    
                                     
NEWBL 03-13 05:53:04 32432 355.8134504                                          
NEWBL 03-13 04:53:25 32433 214.92115141                                       
NEWBL 03-13 04:53:59 32434 393.64978061

3 block ?  a minute ><;;
                                      
NEWBL 03-13 04:59:14 32435 818.01887486                                       
NEWBL 03-13 05:00:29 32436 393.76064966 

[Wh1teKn1ght]

hey guys, just wondering your opinion on what will happen to DRK once stealth addresses are introduced into bitcoin? WOn't that take away DRK's advantage of providing anonymity?

[eltito]

DarkSend Beta Version 3.5 (v8.9.7)

- Session ID's are now tied to the blockHeight, so they'll be much more stable. Some users were reporting stale DarkSend messages all of the time because they couldn't sync.

Documentation:
http://darkcoin.io/downloads/DarkSendv3.pdf
http[Suspicious link removed]] http[Suspicious link removed][/url]
Ubuntu 64 qt: http://darkcoin.io/downloads/beta/darkcoin-qt
Ubuntu 64 daemon: http://darkcoin.io/downloads/beta/darkcoind

What's Next?
The next update is going to be a big one, it'll probably take me a week maybe.

Currently the network uses 1 master node, so it's a centralized implementation. I'm going to write some tamper proof logic to pick a random node from the network and elect it as the master. This is a neat implementation, because when you leave on your client it supports the network and you'll randomly receive fees when people try to attack DarkSend ( or turn off their clients in mid-transaction, lose their internet connection, etc ). We should see a really healthy amount of full nodes because of this, maybe even more than Bitcoin itself eventually.

I may want to make out with you.  But totally not in a gay way.

[mattmct]

Awesome work Evan!

I'm looking forward to the "big" update!  I'm running and will be running future wallets hoping to be picked as a node haha.

[ErrorId]

Anyone else seeing 10K difficulty?

[tifozi]

Dat difficulty



only for a block though it seems.

Code:

NEWBL 03-13 04:52:10 32430 344.18513048                                         
NEWBL 03-13 04:52:48 32431 351.97650267    
                                     
NEWBL 03-13 05:53:04 32432 355.8134504                                          
NEWBL 03-13 04:53:25 32433 214.92115141                                       
NEWBL 03-13 04:53:59 32434 393.64978061

3 block ?  a minute ><;;
                                      
NEWBL 03-13 04:59:14 32435 818.01887486                                       
NEWBL 03-13 05:00:29 32436 393.76064966 

With all the good info coming in, sad to see mining become tougher and tougher everyday. 2GH got added in last hour.

Code:

{
    "blocks" : 32457,
    "currentblocksize" : 1451,
    "currentblocktx" : 2,
    "difficulty" : 575.52590268,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "networkhashps" : 11429906792,
    "pooledtx" : 2,
    "testnet" : false
}

[chaeplin]

diff : 10048


 

[mattmct]

Anyone else seeing 10K difficulty?

Nope, going high though.  Seen it between 400 - 800 over the past few mins.

"blocks" : 32460,
"timeoffset" : -1,
"connections" : 8,
"proxy" : "",
"difficulty" : 420.14875661,

[tifozi]

@eddufield

What methods are new with darksend in the daemon ? I was trying to see how to darksend works darkcoind but --help just gives the usual info.

[chaeplin]

Anyone else seeing 10K difficulty?

Nope, going high though.  Seen it between 400 - 800 over the past few mins.

"blocks" : 32460,
"timeoffset" : -1,
"connections" : 8,
"proxy" : "",
"difficulty" : 420.14875661,

    "coinbasevalue" : 1901000000,
    "target" : "000000000006859c000000000000000000000000000000000000000000000000",
    "mintime" : 1394656609,
    "mutable" : [
        "time",
        "transactions",
        "prevblock"
    ],
    "noncerange" : "00000000ffffffff",
    "sigoplimit" : 20000,
    "sizelimit" : 1000000,
    "curtime" : 1394658568,
    "bits" : "1b06859c",
    "height" : 32461

target