planet earth,
get ready...
because...
DRK is coming!
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 4470. (Read 9723733 times)
August 12, 2014, 12:10:18 AM
planet earth,
get ready...
because...
DRK is coming!
August 11, 2014, 11:12:52 PM
I'm pretty sure the Deathstar is a fitting analogy (minus the blowing up part. We've got that covered
).An email I just sent to Kristov explaining how the pairing strategy works:
the goal is for all participants to use the same denominations, so you can't tell who's are whos afterward.
For example, here's one approved pairing:
Bob: 500, 100, 100, 100, 10, 10
Mary: 500, 100, 100, 10
Joe 500, 100, 10
Another
Bob: 100, 100, 100, 10, 10, 1
Mary:100, 100, 10, 1
Joe 100, 10, 1, 1, 1
This means that if one has a 500DRK output, they all must have one. If one has a 100DRK output, they must all have at least one.
So the way this is accomplished is very complicated, I've attached the newest source and I'll point you to the correct locations where things are happening.
The flow of events is like this:
1.) DoAutomaticDenominating is executed, inputs are queried to see what work needs to be done (main.cpp:7080). The total amount is added up at main.cpp:7114, then this is fed into GetDenominationsByAmount. GetDenominationsByAmount creates a unique integer via bitshifting for each combination of inputs (main.cpp:7533, main.cpp:7527). So that integer can be recreated by another client pretty easily without having to pass the entire datastructure all around the network (std::vector
2.) A DSA (Darksend Acceptable main.cpp:3928) is sent to a masternode with the total value that is going to be submitted. The next thing that happens is the masternode sees if it has any active sessions (main.cpp:7487), if it does it uses a few session variables. This is then fed into GetDenomationsByAmount, which gives us that bitshifted integer again.
3.) The masternode sends out a DarksendQueue object stating it's open for business, along with the bitshifted integer (main.cpp:6377). Then the next client when they run DoAutomaticDenomination, they'll look through those objects and see if they're compatible with any of the open sessions (main.cpp:7119). So as a result, we get to let clients pick the masternodes they use randomly and can use the entire network at once for all of the different combinations of denominations (which I'm really excited about, this is something that's been hard to achieve!).
4.) Then the signing begins and all of that jazz
Very nice, this is a very elegant solution. Quite impressive. Respect.
August 11, 2014, 11:09:07 PM
I'm pretty sure the Deathstar is a fitting analogy (minus the blowing up part. We've got that covered
).An email I just sent to Kristov explaining how the pairing strategy works:
the goal is for all participants to use the same denominations, so you can't tell who's are whos afterward.
For example, here's one approved pairing:
Bob: 500, 100, 100, 100, 10, 10
Mary: 500, 100, 100, 10
Joe 500, 100, 10
Another
Bob: 100, 100, 100, 10, 10, 1
Mary:100, 100, 10, 1
Joe 100, 10, 1, 1, 1
This means that if one has a 500DRK output, they all must have one. If one has a 100DRK output, they must all have at least one.
So the way this is accomplished is very complicated, I've attached the newest source and I'll point you to the correct locations where things are happening.
The flow of events is like this:
1.) DoAutomaticDenominating is executed, inputs are queried to see what work needs to be done (main.cpp:7080). The total amount is added up at main.cpp:7114, then this is fed into GetDenominationsByAmount. GetDenominationsByAmount creates a unique integer via bitshifting for each combination of inputs (main.cpp:7533, main.cpp:7527). So that integer can be recreated by another client pretty easily without having to pass the entire datastructure all around the network (std::vector
2.) A DSA (Darksend Acceptable main.cpp:3928) is sent to a masternode with the total value that is going to be submitted. The next thing that happens is the masternode sees if it has any active sessions (main.cpp:7487), if it does it uses a few session variables. This is then fed into GetDenomationsByAmount, which gives us that bitshifted integer again.
3.) The masternode sends out a DarksendQueue object stating it's open for business, along with the bitshifted integer (main.cpp:6377). Then the next client when they run DoAutomaticDenomination, they'll look through those objects and see if they're compatible with any of the open sessions (main.cpp:7119). So as a result, we get to let clients pick the masternodes they use randomly and can use the entire network at once for all of the different combinations of denominations (which I'm really excited about, this is something that's been hard to achieve!).
4.) Then the signing begins and all of that jazz
Very nice, this is a very elegant solution. Quite impressive. Respect.
August 11, 2014, 11:03:54 PM
Wow, its been a long time since we had so much regurgitated brown semen trolls in here... Evan must be making some progress on RC4.
Yup. Did you know that now we are now tied to the fate Bitcoin like everyone else? I saw,the wailing several pages back. My gawd this idiot made a spectacle of himself... Ruined his life? Pathetic... I don't even want to make fun of him... I'm not sure its possible after what he's done to himsrlf. I want to give him a hug...
August 11, 2014, 10:59:57 PM
Wow, its been a long time since we had so much regurgitated brown semen trolls in here... Evan must be making some progress on RC4.
Yup. Did you know that now we are now tied to the fate Bitcoin like everyone else?
You are such an asshole. You just can't let it go can you?
Not until faggot trolls stop trying to manipulate in this thread and I defud for everyone to see what they do, and how they do it. Rest is up to them. You will get over it. We will see more concerns and negative nancying from you I am sure. I can play all day.
August 11, 2014, 10:57:40 PM
Bromantic....
August 11, 2014, 10:53:49 PM
thanks duffmiester and well done once again
August 11, 2014, 10:52:28 PM
I'm pretty sure the Deathstar is a fitting analogy (minus the blowing up part. We've got that covered
).An email I just sent to Kristov explaining how the pairing strategy works:
the goal is for all participants to use the same denominations, so you can't tell who's are whos afterward.
For example, here's one approved pairing:
Bob: 500, 100, 100, 100, 10, 10
Mary: 500, 100, 100, 10
Joe 500, 100, 10
Another
Bob: 100, 100, 100, 10, 10, 1
Mary:100, 100, 10, 1
Joe 100, 10, 1, 1, 1
This means that if one has a 500DRK output, they all must have one. If one has a 100DRK output, they must all have at least one.
So the way this is accomplished is very complicated, I've attached the newest source and I'll point you to the correct locations where things are happening.
The flow of events is like this:
1.) DoAutomaticDenominating is executed, inputs are queried to see what work needs to be done (main.cpp:7080). The total amount is added up at main.cpp:7114, then this is fed into GetDenominationsByAmount. GetDenominationsByAmount creates a unique integer via bitshifting for each combination of inputs (main.cpp:7533, main.cpp:7527). So that integer can be recreated by another client pretty easily without having to pass the entire datastructure all around the network (std::vector
2.) A DSA (Darksend Acceptable main.cpp:3928) is sent to a masternode with the total value that is going to be submitted. The next thing that happens is the masternode sees if it has any active sessions (main.cpp:7487), if it does it uses a few session variables. This is then fed into GetDenomationsByAmount, which gives us that bitshifted integer again.
3.) The masternode sends out a DarksendQueue object stating it's open for business, along with the bitshifted integer (main.cpp:6377). Then the next client when they run DoAutomaticDenomination, they'll look through those objects and see if they're compatible with any of the open sessions (main.cpp:7119). So as a result, we get to let clients pick the masternodes they use randomly and can use the entire network at once for all of the different combinations of denominations (which I'm really excited about, this is something that's been hard to achieve!).
4.) Then the signing begins and all of that jazz
Question 1: how does network now determine that MN is legit and has 1000 Drks in it? i.e. how are fake MNs detected.
Question 2: any comments on potentially larger blockchain? i.e. calcs done on extra transactions etc...
Question 3: Do you sleep?
August 11, 2014, 10:42:11 PM
Wow, its been a long time since we had so much regurgitated brown semen trolls in here... Evan must be making some progress on RC4.
lol, where you been, too many people quoting trolls today when we should be focusing on rc4. 
August 11, 2014, 10:41:23 PM
I'm pretty sure the Deathstar is a fitting analogy (minus the blowing up part. We've got that covered
).An email I just sent to Kristov explaining how the pairing strategy works:
the goal is for all participants to use the same denominations, so you can't tell who's are whos afterward.
For example, here's one approved pairing:
Bob: 500, 100, 100, 100, 10, 10
Mary: 500, 100, 100, 10
Joe 500, 100, 10
Another
Bob: 100, 100, 100, 10, 10, 1
Mary:100, 100, 10, 1
Joe 100, 10, 1, 1, 1
This means that if one has a 500DRK output, they all must have one. If one has a 100DRK output, they must all have at least one.
So the way this is accomplished is very complicated, I've attached the newest source and I'll point you to the correct locations where things are happening.
The flow of events is like this:
1.) DoAutomaticDenominating is executed, inputs are queried to see what work needs to be done (main.cpp:7080). The total amount is added up at main.cpp:7114, then this is fed into GetDenominationsByAmount. GetDenominationsByAmount creates a unique integer via bitshifting for each combination of inputs (main.cpp:7533, main.cpp:7527). So that integer can be recreated by another client pretty easily without having to pass the entire datastructure all around the network (std::vector
2.) A DSA (Darksend Acceptable main.cpp:3928) is sent to a masternode with the total value that is going to be submitted. The next thing that happens is the masternode sees if it has any active sessions (main.cpp:7487), if it does it uses a few session variables. This is then fed into GetDenomationsByAmount, which gives us that bitshifted integer again.
3.) The masternode sends out a DarksendQueue object stating it's open for business, along with the bitshifted integer (main.cpp:6377). Then the next client when they run DoAutomaticDenomination, they'll look through those objects and see if they're compatible with any of the open sessions (main.cpp:7119). So as a result, we get to let clients pick the masternodes they use randomly and can use the entire network at once for all of the different combinations of denominations (which I'm really excited about, this is something that's been hard to achieve!).
4.) Then the signing begins and all of that jazz
August 11, 2014, 10:37:37 PM
Wow, its been a long time since we had so much regurgitated brown semen trolls in here... Evan must be making some progress on RC4.
Yup. Did you know that now we are now tied to the fate Bitcoin like everyone else?
You are such an asshole. You just can't let it go can you?
August 11, 2014, 10:36:32 PM
Wow, its been a long time since we had so much regurgitated brown semen trolls in here... Evan must be making some progress on RC4.
lol, where you been, too many people quoting trolls today when we should be focusing on rc4. August 11, 2014, 10:34:47 PM
Wow, its been a long time since we had so much regurgitated brown semen trolls in here... Evan must be making some progress on RC4.
lol, where you been, too many people quoting trolls today when we should be focusing on rc4.
August 11, 2014, 10:34:12 PM
Wow, its been a long time since we had so much regurgitated brown semen trolls in here... Evan must be making some progress on RC4.
Yup. Did you know that now we are now tied to the fate Bitcoin like everyone else?
August 11, 2014, 10:31:42 PM
Wow, its been a long time since we had so much regurgitated brown semen trolls in here... Evan must be making some progress on RC4.
Since RC4 has taken a little longer to ripen than anticipated, I managed to fire a few more harpoons... Mmm such tasty, cheap DRKs...
Since RC4 has taken a little longer to ripen than anticipated, I managed to fire a few more harpoons... Mmm such tasty, cheap DRKs...
August 11, 2014, 10:26:36 PM
around 8.30pm today, roughly 5 coins, bc,doge,ltc,drk,clk were all dumped, then btc was dumped for usd. What we have is a whale or whale group cashing out..around 2000+ btc.
August 11, 2014, 10:24:18 PM
Pretty shitty day for major alts:
1 Bitcoin Bitcoin $ 7,558,980,892 $ 575.71 13,129,750 BTC $ 15,634,900 -2.40 %
2 Litecoin Litecoin $ 175,078,004 $ 5.64 31,055,304 LTC $ 7,791,980 -18.89 %
3 Ripple Ripple $ 42,871,930 $ 0.005195 8,252,600,677 XRP * $ 294,352 4.62 %
4 Nxt Nxt $ 32,851,405 $ 0.032851 999,997,096 NXT * $ 148,855 -11.26 %
5 Darkcoin Darkcoin $ 22,945,342 $ 5.04 4,551,717 DRK $ 222,400 -9.11 %
6 Peercoin Peercoin $ 18,664,494 $ 0.862854 21,631,114 PPC $ 171,565 -10.44 %
7 BitSharesX BitSharesX $ 17,337,031 $ 0.008669 1,999,775,140 BTSX * $ 74,543 -3.39 %
8 Dogecoin Dogecoin $ 12,596,578 $ 0.000141 89,541,278,777 DOGE $ 234,752 -14.98 %
9 MaidSafeCoin MaidSafeCoin $ 12,344,725 $ 0.027278 452,552,412 MAID * $ 29,963 2.52 %
10 Namecoin Namecoin $ 12,300,611 $ 1.29 9,570,300 NMC $ 107,895 -9.31 %
1 Bitcoin Bitcoin $ 7,558,980,892 $ 575.71 13,129,750 BTC $ 15,634,900 -2.40 %
2 Litecoin Litecoin $ 175,078,004 $ 5.64 31,055,304 LTC $ 7,791,980 -18.89 %
3 Ripple Ripple $ 42,871,930 $ 0.005195 8,252,600,677 XRP * $ 294,352 4.62 %
4 Nxt Nxt $ 32,851,405 $ 0.032851 999,997,096 NXT * $ 148,855 -11.26 %
5 Darkcoin Darkcoin $ 22,945,342 $ 5.04 4,551,717 DRK $ 222,400 -9.11 %
6 Peercoin Peercoin $ 18,664,494 $ 0.862854 21,631,114 PPC $ 171,565 -10.44 %
7 BitSharesX BitSharesX $ 17,337,031 $ 0.008669 1,999,775,140 BTSX * $ 74,543 -3.39 %
8 Dogecoin Dogecoin $ 12,596,578 $ 0.000141 89,541,278,777 DOGE $ 234,752 -14.98 %
9 MaidSafeCoin MaidSafeCoin $ 12,344,725 $ 0.027278 452,552,412 MAID * $ 29,963 2.52 %
10 Namecoin Namecoin $ 12,300,611 $ 1.29 9,570,300 NMC $ 107,895 -9.31 %
DRK Very Soon ----» http://media2.giphy.com/media/J6xbWpR4kKaME/200.gif
Maybe but it seems we're tied like everyone else to the fate of bitcoin. Bitcoin has stagnated as of late and appears to be moving down.
August 11, 2014, 10:21:29 PM
Pretty shitty day for major alts:
1 Bitcoin Bitcoin $ 7,558,980,892 $ 575.71 13,129,750 BTC $ 15,634,900 -2.40 %
2 Litecoin Litecoin $ 175,078,004 $ 5.64 31,055,304 LTC $ 7,791,980 -18.89 %
3 Ripple Ripple $ 42,871,930 $ 0.005195 8,252,600,677 XRP * $ 294,352 4.62 %
4 Nxt Nxt $ 32,851,405 $ 0.032851 999,997,096 NXT * $ 148,855 -11.26 %
5 Darkcoin Darkcoin $ 22,945,342 $ 5.04 4,551,717 DRK $ 222,400 -9.11 %
6 Peercoin Peercoin $ 18,664,494 $ 0.862854 21,631,114 PPC $ 171,565 -10.44 %
7 BitSharesX BitSharesX $ 17,337,031 $ 0.008669 1,999,775,140 BTSX * $ 74,543 -3.39 %
8 Dogecoin Dogecoin $ 12,596,578 $ 0.000141 89,541,278,777 DOGE $ 234,752 -14.98 %
9 MaidSafeCoin MaidSafeCoin $ 12,344,725 $ 0.027278 452,552,412 MAID * $ 29,963 2.52 %
10 Namecoin Namecoin $ 12,300,611 $ 1.29 9,570,300 NMC $ 107,895 -9.31 %
1 Bitcoin Bitcoin $ 7,558,980,892 $ 575.71 13,129,750 BTC $ 15,634,900 -2.40 %
2 Litecoin Litecoin $ 175,078,004 $ 5.64 31,055,304 LTC $ 7,791,980 -18.89 %
3 Ripple Ripple $ 42,871,930 $ 0.005195 8,252,600,677 XRP * $ 294,352 4.62 %
4 Nxt Nxt $ 32,851,405 $ 0.032851 999,997,096 NXT * $ 148,855 -11.26 %
5 Darkcoin Darkcoin $ 22,945,342 $ 5.04 4,551,717 DRK $ 222,400 -9.11 %
6 Peercoin Peercoin $ 18,664,494 $ 0.862854 21,631,114 PPC $ 171,565 -10.44 %
7 BitSharesX BitSharesX $ 17,337,031 $ 0.008669 1,999,775,140 BTSX * $ 74,543 -3.39 %
8 Dogecoin Dogecoin $ 12,596,578 $ 0.000141 89,541,278,777 DOGE $ 234,752 -14.98 %
9 MaidSafeCoin MaidSafeCoin $ 12,344,725 $ 0.027278 452,552,412 MAID * $ 29,963 2.52 %
10 Namecoin Namecoin $ 12,300,611 $ 1.29 9,570,300 NMC $ 107,895 -9.31 %
DRK Very Soon ----»
August 11, 2014, 10:11:01 PM
Pretty shitty day for major alts:
1 Bitcoin Bitcoin $ 7,558,980,892 $ 575.71 13,129,750 BTC $ 15,634,900 -2.40 %
2 Litecoin Litecoin $ 175,078,004 $ 5.64 31,055,304 LTC $ 7,791,980 -18.89 %
3 Ripple Ripple $ 42,871,930 $ 0.005195 8,252,600,677 XRP * $ 294,352 4.62 %
4 Nxt Nxt $ 32,851,405 $ 0.032851 999,997,096 NXT * $ 148,855 -11.26 %
5 Darkcoin Darkcoin $ 22,945,342 $ 5.04 4,551,717 DRK $ 222,400 -9.11 %
6 Peercoin Peercoin $ 18,664,494 $ 0.862854 21,631,114 PPC $ 171,565 -10.44 %
7 BitSharesX BitSharesX $ 17,337,031 $ 0.008669 1,999,775,140 BTSX * $ 74,543 -3.39 %
8 Dogecoin Dogecoin $ 12,596,578 $ 0.000141 89,541,278,777 DOGE $ 234,752 -14.98 %
9 MaidSafeCoin MaidSafeCoin $ 12,344,725 $ 0.027278 452,552,412 MAID * $ 29,963 2.52 %
10 Namecoin Namecoin $ 12,300,611 $ 1.29 9,570,300 NMC $ 107,895 -9.31 %
1 Bitcoin Bitcoin $ 7,558,980,892 $ 575.71 13,129,750 BTC $ 15,634,900 -2.40 %
2 Litecoin Litecoin $ 175,078,004 $ 5.64 31,055,304 LTC $ 7,791,980 -18.89 %
3 Ripple Ripple $ 42,871,930 $ 0.005195 8,252,600,677 XRP * $ 294,352 4.62 %
4 Nxt Nxt $ 32,851,405 $ 0.032851 999,997,096 NXT * $ 148,855 -11.26 %
5 Darkcoin Darkcoin $ 22,945,342 $ 5.04 4,551,717 DRK $ 222,400 -9.11 %
6 Peercoin Peercoin $ 18,664,494 $ 0.862854 21,631,114 PPC $ 171,565 -10.44 %
7 BitSharesX BitSharesX $ 17,337,031 $ 0.008669 1,999,775,140 BTSX * $ 74,543 -3.39 %
8 Dogecoin Dogecoin $ 12,596,578 $ 0.000141 89,541,278,777 DOGE $ 234,752 -14.98 %
9 MaidSafeCoin MaidSafeCoin $ 12,344,725 $ 0.027278 452,552,412 MAID * $ 29,963 2.52 %
10 Namecoin Namecoin $ 12,300,611 $ 1.29 9,570,300 NMC $ 107,895 -9.31 %
August 11, 2014, 10:07:06 PM
The Death Star is more like the Ghash pool.
Jump to: