oh man...
{
"blocks" : 32461,
"currentblocksize" : 1825,
"currentblocktx" : 3,
"difficulty" : 10048.43423331,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 12589130728,
"pooledtx" : 3,
"testnet" : false
}
http://darkcoin.mine.nu/graph.html
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 6603. (Read 9724017 times)
March 12, 2014, 04:37:27 PM
March 12, 2014, 04:31:51 PM
@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.
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.
Nothing cosmetic was changed, it was all internal.
March 12, 2014, 04:26:17 PM
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,
Quote
"coinbasevalue" : 1901000000,
"target" : "000000000006859c000000000000000000000000000000000000000000000000",
"mintime" : 1394656609,
"mutable" : [
"time",
"transactions",
"prevblock"
],
"noncerange" : "00000000ffffffff",
"sigoplimit" : 20000,
"sizelimit" : 1000000,
"curtime" : 1394658568,
"bits" : "1b06859c",
"height" : 32461
"target" : "000000000006859c000000000000000000000000000000000000000000000000",
"mintime" : 1394656609,
"mutable" : [
"time",
"transactions",
"prevblock"
],
"noncerange" : "00000000ffffffff",
"sigoplimit" : 20000,
"sizelimit" : 1000000,
"curtime" : 1394658568,
"bits" : "1b06859c",
"height" : 32461
target
DRK network hashrate (estimate): 287.72 GH/s Network block difficulty: 10048.434 (658.53 M)
p2pool... we stuck here ?
March 12, 2014, 04:18:47 PM
diff : 10048
K, not just me then, thought I was seeing that wrong. Anyone know how much hashing power it takes to jump from 400s to 10k?
With the regular increments in which this happens, I'm starting to think that these repetitive . . random spikes are due to a bug in the difficulty retargeting . . or we just got really lucky and solved enough blocks in such a fast time that the retarget put it so high. Either way . . it's at 10k now and that doesn't seem very good.
March 12, 2014, 04:10:23 PM
diff : 10048
K, not just me then, thought I was seeing that wrong. Anyone know how much hashing power it takes to jump from 400s to 10k?
March 12, 2014, 04:10:23 PM
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,
Quote
"coinbasevalue" : 1901000000,
"target" : "000000000006859c000000000000000000000000000000000000000000000000",
"mintime" : 1394656609,
"mutable" : [
"time",
"transactions",
"prevblock"
],
"noncerange" : "00000000ffffffff",
"sigoplimit" : 20000,
"sizelimit" : 1000000,
"curtime" : 1394658568,
"bits" : "1b06859c",
"height" : 32461
"target" : "000000000006859c000000000000000000000000000000000000000000000000",
"mintime" : 1394656609,
"mutable" : [
"time",
"transactions",
"prevblock"
],
"noncerange" : "00000000ffffffff",
"sigoplimit" : 20000,
"sizelimit" : 1000000,
"curtime" : 1394658568,
"bits" : "1b06859c",
"height" : 32461
target
March 12, 2014, 04:06:34 PM
@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.
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.
March 12, 2014, 04:02:54 PM
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,
March 12, 2014, 04:02:30 PM
diff : 10048
March 12, 2014, 04:02:13 PM
Dat difficulty
only for a block though it seems.
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
}
March 12, 2014, 04:01:20 PM
Anyone else seeing 10K difficulty?
March 12, 2014, 03:59:11 PM
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.
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.
March 12, 2014, 03:49:06 PM
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.
- 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.
March 12, 2014, 03:45:47 PM
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?
March 12, 2014, 03:29:02 PM
Dat difficulty
only for a block though it seems.
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
March 12, 2014, 03:27:59 PM
Session_ID seems to be stuck at 1000. Any nodes to be added?
Edit: spoke too soon. Executed a successful DarkSend
Edit: spoke too soon. Executed a successful DarkSend
March 12, 2014, 03:27:18 PM
March 12, 2014, 03:24:56 PM
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.
- 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
March 12, 2014, 03:22:37 PM
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.
- 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!
March 12, 2014, 03:15:56 PM
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.
- 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.
Jump to: