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

[camosoul]

No causal link is provable

Of course, that's why it's called casual...

Casual == Plausible, and nothing stops a government, especially one already operating under the premise, to substitute Plausible Cause for Probable Cause.

[camosoul]

Kristov Atlas has agreed to be the first to review the Darksend code. Kristov will be evaluating anonymity and overall design of our technology and will report his findings publicly. We’ll be sending the code to him soon and we anticipate that we will hear back from Kristov by the end of the month.

Hope he doesn't decide to take it upon himself to Open Source it against Evan's will...

[naxin]

I still think that my red chunks example still applies... Since I can differentiate between an MN and a Client by noting that one doesn't ever perform a TX and one does, there really is no mixing... Thus, I can aggregate the signatures that match each other to find the total value of the TX.

Ahh, I see where your hangup is now. You misunderstand how MNs work.

The masternode doesn't leave a trace on the transactions, there is no way to determine whether a tx was related to a masternode or not.

Essentially you are sending a 1 DRK output from a tainted address and get 1 DRK back to a different address, however it is in your wallet (but your wallet only exists in your client, it is not public, and old keys can be deleted). The masternode simply facilitates this transfer.

[splawik21]

I don't know about you but I'm instaminising darkcoin NOW!

[JGCMiner]

Nice work by the dev team.  

As always please update the first post and also I think that it is important to advertise Darksend+ in the title rather than masternode payments. That needs a change as well.

As for Kristov stealing (or pre-releasing) the code, I suspect that he won't -- but the dev team would be wise to take appropriate measures to prevent this from happening.

[patrolman]

I still think that my red chunks example still applies... Since I can differentiate between an MN and a Client by noting that one doesn't ever perform a TX and one does, there really is no mixing... Thus, I can aggregate the signatures that match each other to find the total value of the TX.

Ahh, I see where your hangup is now. You misunderstand how MNs work.

The masternode doesn't leave a trace on the transactions, there is no way to determine whether a tx was related to a masternode or not.

Essentially you are sending a 1 DRK output from a tainted address and get 1 DRK back to a different address, however it is in your wallet (but your wallet only exists in your client, it is not public, and old keys can be deleted). The masternode simply facilitates this transfer.

It's probably been addressed, but what happens if a masternode goes offline in the process?

[camosoul]

I still think that my red chunks example still applies... Since I can differentiate between an MN and a Client by noting that one doesn't ever perform a TX and one does, there really is no mixing... Thus, I can aggregate the signatures that match each other to find the total value of the TX.

Ahh, I see where your hangup is now. You misunderstand how MNs work.

The masternode doesn't leave a trace on the transactions, there is no way to determine whether a tx was related to a masternode or not.

Essentially you are sending a 1 DRK output from a tainted address and get 1 DRK back to a different address, however it is in your wallet (but your wallet only exists in your client, it is not public, and old keys can be deleted). The masternode simply facilitates this transfer.

It's been stated several times that masternodes leave a lot more than a trace. It's one thing to misunderstand it, another to read it 50+ times from official outlets...

OTOH...

Whether or not my questions are answered satisfactorily is a factor of my own ability to understand. If I'm just too stupid to figure it out, at least it serves as an example to others who might, lols.

[camosoul]

advertise Darksend+ in the title rather than masternode payments.

This!

Advertising masternode payments is like saying "miners get paid sometimes!" PoW already tells you that much...

PoService already tells us that MNs get paid...

So, simply being DRK already tells us these things, lets advertise how it works instead...

[toknormal]

No FUD anymore because the fudsters have all bought back in.  

(Or are trying to)

[thunderdrum]

Only if rc4 works, i hope that. but rc2 fail ad rc3 fail two times. RC4 please make me happy  

 RC2 failing was a blessing in disguise. Great success only comes after great failures = great innovations in the protocol !!

 RC3 did not fail. It was a responsible revert by the dev. Mini-forks did happen, and network consensus would have been achieved. There were clear bad intentioned actors trying to subvert the network. It was reverted because too many miners would have been hurt. The bad blocks were orphaned in a longer time than block generation, so it would end up 100% fine... except too many miners would see their mining profits DEDUCED. So Evan reverted, because miners are the most important group to secure the network. That also brought spectacular improvements. (for example,  yet another innovative and brilliant spork solution instead of fork)

 RC4 has not happened yet, but with 99% of pools upgraded, already at 88% MN payout, by tomorrow 97-99%, only multipools, insta-profit-dumpers and whales are pushing the price down, at extremely low volume... every day... slowly... for almost a month now... and I couldnt care less (because I have no BTC to buy more if not I'd love it!!)

 Big money is obviously waiting for the fork, to jump in. Rocket launch to the moon when code is vetted and released.

 Dump!! please do!!

Development Updates - July 15th

https://darkcointalk.org/threads/development-updates-july-15th.1788/

thank you for posting..looking forward to reading

Bravo~！ Bravo~！Bravo~！

That't why DRK will be the final winner in the crypto world.
We have a brilliant dev team that means INNOVATION.
We have a firmly community with so many smart people with most of the DRK which means SAGACITY.

 

[Ignition75]

i'm starting to feel an urge to just set time two weeks ahead and be done with it all .. all this tension is getting to me.
eh, any new fitness girls dancing the darkcoin dance ? or something new.. new is good too

This tension is awesome...  In the lead up to RC4 difficulty and price is down... Last chance saloon to buy and mine and crazy low prices/difficulty...

[stealth923]

Development Updates - July 15th

https://darkcointalk.org/threads/development-updates-july-15th.1788/

thank you for posting..looking forward to reading

Bravo~！ Bravo~！Bravo~！

WHOAAAAAAA this happens while i sleep - insane - Kirstov Atlas - Darksend+.......I cannot wait till RC4
Im dedicating all my miners to testnet when it comes up 60mh+

[GhostPlayer]

 Exactly as predicted

 93.9% network compliance!! In a few hours it will be 99%

 

[aleix]

hey Kristov, thanks for reviewing "our" code. I know you are reading 

A lot of people, not only the devs, are doing a lot of hard work for this to succeed. Ghost, our President, Propulsion, Tante, Alex, Camo, Tok, Coins, our beloved trolls, our team of troll-hunters, and many others.

We expect a lot from you, do it fair and do it well 

[naxin]

I still think that my red chunks example still applies... Since I can differentiate between an MN and a Client by noting that one doesn't ever perform a TX and one does, there really is no mixing... Thus, I can aggregate the signatures that match each other to find the total value of the TX.

Ahh, I see where your hangup is now. You misunderstand how MNs work.

The masternode doesn't leave a trace on the transactions, there is no way to determine whether a tx was related to a masternode or not.

Essentially you are sending a 1 DRK output from a tainted address and get 1 DRK back to a different address, however it is in your wallet (but your wallet only exists in your client, it is not public, and old keys can be deleted). The masternode simply facilitates this transfer.

It's been stated several times that masternodes leave a lot more than a trace. It's one thing to misunderstand it, another to read it 50+ times from official outlets...

OTOH...

Whether or not my questions are answered satisfactorily is a factor of my own ability to understand. If I'm just too stupid to figure it out, at least it serves as an example to others who might, lols.

You do raise a valid concern in that how exactly the functionality works needs to be communicated better.

As for MNs leaving a trace or not, let me play around with some transactions and see how it works in practice. I need to think a bit. However I still am quite confident this is a non-issue, but I do want to figure out a much better way to articulate the process so anyone could understand it (let alone someone who has historically had a lot of confidence in darkcoin and only the best intentions -- you)

[coins101]

hey Kristov, thanks for reviewing "our" code. I know you are reading 

A lot of people, not only the devs, are doing a lot of hard work for this to succeed. Ghost, our President, Propulsion, Tante, Alex, Camo, Tok, Coins, our beloved trolls, our team of troll-hunters, and many others.

We expect a lot from you, do it fair and do it well 

+101

And post your DRK address for donations.

[JGCMiner]

I still think that my red chunks example still applies... Since I can differentiate between an MN and a Client by noting that one doesn't ever perform a TX and one does, there really is no mixing... Thus, I can aggregate the signatures that match each other to find the total value of the TX.

Ahh, I see where your hangup is now. You misunderstand how MNs work.

The masternode doesn't leave a trace on the transactions, there is no way to determine whether a tx was related to a masternode or not.

Essentially you are sending a 1 DRK output from a tainted address and get 1 DRK back to a different address, however it is in your wallet (but your wallet only exists in your client, it is not public, and old keys can be deleted). The masternode simply facilitates this transfer.

It's been stated several times that masternodes leave a lot more than a trace. It's one thing to misunderstand it, another to read it 50+ times from official outlets...

OTOH...

Whether or not my questions are answered satisfactorily is a factor of my own ability to understand. If I'm just too stupid to figure it out, at least it serves as an example to others who might, lols.

You do raise a valid concern in that how exactly the functionality works needs to be communicated better.

As for MNs leaving a trace or not, let me play around with some transactions and see how it works in practice. I need to think a bit. However I still am quite confident this is a non-issue, but I do want to figure out a much better way to articulate the process so anyone could understand it (let alone someone who has historically had a lot of confidence in darkcoin and only the best intentions -- you)

Some more info from Evan would be nice, but maybe he is keeping the biggest trade secrets underwraps until Darksend+ launch. Makes since as we are getting really close. RC4 testing and the code review will be going on simultaneously -- and when that is finished RC4 will be released followed by the Darksend+ release.  

[stealth923]

hey Kristov, thanks for reviewing "our" code. I know you are reading 

A lot of people, not only the devs, are doing a lot of hard work for this to succeed. Ghost, our President, Propulsion, Tante, Alex, Camo, Tok, Coins, our beloved trolls, our team of troll-hunters, and many others.

We expect a lot from you, do it fair and do it well 

+101

And post your DRK address for donations.

+1 I am happy to donate a couple of weeks worth of masternode payments to Kristov

[stealth923]

hey Kristov, thanks for reviewing "our" code. I know you are reading 

A lot of people, not only the devs, are doing a lot of hard work for this to succeed. Ghost, our President, Propulsion, Tante, Alex, Camo, Tok, Coins, our beloved trolls, our team of troll-hunters, and many others.

We expect a lot from you, do it fair and do it well 

+101

And post your DRK address for donations.

+1 I am happy to donate a couple of weeks worth of masternode payments to Kristov

Actually we should aim to gift Kristov with at least 1 masternode for reviewing the code!

Let him be a masternode owner and part of the community!

[toknormal]

Let him be a masternode owner and part of the community!

Wouldn't that amount to bribery ?

Isn't he supposed to be impartial ?