Author

Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 4740. (Read 9723847 times)

member
Activity: 70
Merit: 10
Some Interesting Facts on Cryptocurrency Traders
1: average age is 20years
2: single male
3:speed trade (looking to make enough to pay rent)

I feel like a grandpa. here  Smiley


hero member
Activity: 611
Merit: 500
Let him be a masternode owner and part of the community!

Wouldn't that amount to bribery ?

Isn't he supposed to be impartial ?


Well I think the donation address was Kristov's idea as he is short on time and "time is money". If he uses those donations towards a MN then that is his business, right?

Don't think anybody is attempting bribery.

legendary
Activity: 966
Merit: 1000
Let him be a masternode owner and part of the community!

Wouldn't that amount to bribery ?

Isn't he supposed to be impartial ?


Yeah I think he should pay us.  Kiss
legendary
Activity: 3066
Merit: 1188
Let him be a masternode owner and part of the community!

Wouldn't that amount to bribery ?

Isn't he supposed to be impartial ?
legendary
Activity: 1036
Merit: 1000
hey Kristov, thanks for reviewing "our" code. I know you are reading  Grin

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  Wink

+101

And post your DRK address for donations.

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

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!
legendary
Activity: 1036
Merit: 1000
hey Kristov, thanks for reviewing "our" code. I know you are reading  Grin

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  Wink

+101

And post your DRK address for donations.

+1 I am happy to donate a couple of weeks worth of masternode payments to Kristov Cheesy
hero member
Activity: 611
Merit: 500
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.  
legendary
Activity: 1456
Merit: 1000
hey Kristov, thanks for reviewing "our" code. I know you are reading  Grin

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  Wink

+101

And post your DRK address for donations.
full member
Activity: 170
Merit: 100
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)
legendary
Activity: 1790
Merit: 1100
hey Kristov, thanks for reviewing "our" code. I know you are reading  Grin

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  Wink
legendary
Activity: 1092
Merit: 1000
 Exactly as predicted

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

 Grin


legendary
Activity: 1036
Merit: 1000

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+
sr. member
Activity: 462
Merit: 250
www.dashpay.io
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 Smiley


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...
member
Activity: 102
Merit: 10

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

 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!!




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.

 
legendary
Activity: 3066
Merit: 1188

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

(Or are trying to)
hero member
Activity: 560
Merit: 500
www.OroCoin.co
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...
hero member
Activity: 560
Merit: 500
www.OroCoin.co
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.
sr. member
Activity: 447
Merit: 250
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?
hero member
Activity: 611
Merit: 500
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.
legendary
Activity: 1372
Merit: 1005
DASH is the future of crypto payments!
I don't know about you but I'm instaminising darkcoin NOW! Wink
Jump to: