Quote from: solowhizkid on January 06, 2018, 10:54:36 AM

Quote from: iCEBREAKER on January 05, 2018, 10:15:16 PM

Quote from: Bombardier on January 05, 2018, 10:13:03 PM

Quote from: iCEBREAKER on January 05, 2018, 10:09:15 PM

Quote from: falsealarm_bf1 on January 05, 2018, 10:00:07 PM

What's the potential impact from Spectre and Meltdown vulnerabilities to Masternodes running on VPS or Cloud platforms?

https://aws.amazon.com/security/security-bulletins/AWS-2018-013/

tldr; if you had coins in a Masternode hosted on shared VPS they're probably already gone (should have used a Dedicated Instance)

I still have coins in a masternode that's hosted on shared vps. i'll let u know when are gone. stay tuned!

Proof? Signed wallet and Masternode IP please (for 'research' purposes)! Wink

For your info ICEBREAKER, DASH doesn't use hot wallet masternodes that are always online! stop spreading FUD around! Even if a "remote masternode" gets hacked (its a cold wallet) no actual funds are within the wallet, there elsewhere remote probably on the otherside of the world or even on a hardware device like trezor. Stop chatting crap! First learn how Dash's tech works before you start commenting:

Please reread Bombadier's and my posts again, this time paying more attention to the actual words and trying less to be defensive and snippy.

Bombadier had no trouble understanding the meaning of my post and was able to generate a cogent response, so it's obviously your fault that you were unable to correctly parse my post.

Nobody claimed Masternodes use hot wallets; we all understand the basic schema of staking off-line coins.

What I actually said (and Bombadier easily understood) was that Masternodes broadcast their IP address and are thus in danger of losing any coins STORED therein due to Spectre/Meltdown shared VPS exploits.

Let's note that you and solowhizkid entirely failed to acknowledge, must less respond to, the additional claim made here:

Too bad DashCore never got around to making Masternode blinding work. Now Dash users have to worry about zombie Masternodes controlled by Spectre invading their privacy and stealing their coins.

Remember when DashCore had to disable InstantSend for three months and push back the 12.3/Evolution stuff because of an exploit able to be carried out by groups of malicious Masternodes?

You do? Great. Now try to comprehend the fact that now, due to Meltdown/Spectre, Masternodes may be owned by well-meaning derps like you but under the actual control of adversaries.

Guess what that does for the security of InstantSend tx and privacy of PrivateSend tx? Hint: nothing good...

I guess you'll do anything to avoid the topic of Evan's abandoned Masternode blinding initiative. You must be uncomfortable confronting the reality that he promised Masternode blinding, strung gullible suckers like you along with false promises, and then dropped the idea like a hot potato because the computer science/crypto involved are way above his skill level.

Don't feel too bad about being so gullible. At least you are not alone!

Source:

Quote from: smoothie on December 07, 2015, 10:10:11 PM

Quote from: DrkLvr_ on December 07, 2015, 06:50:41 PM

DASH mixing takes a very long time Sad

Months before, Evan made a big deal out of Masternode blinding

Quote from: eduffield on March 03, 2015, 09:14:48 PM

Masternode blinding is working Grin

It's super fast, secure and should reduce mixing time by 80%+

https://github.com/darkcoin/darkcoin/commits/masternode-blinding

Quote from: eduffield on March 10, 2015, 03:40:59 PM

There is NO issue with Darksend, in fact the new masternode blinding system is quite impressive.

Masternode blinding was announced with much fanfare. All the usual suspects were so excited. Just look at how excited GhostPlayer, Toknormal and Minotaur26 were!

But then it was delayed Sad

Quote from: eduffield on April 09, 2015, 08:30:41 PM

************ Please Update To 11.2.22! ****************

- DS Speed Improvements : Darksend should be lightning fast now on mainnet. We're going to delay the implementation of masternode blinding because there's two separate mobile wallets that are in the process of implementing Darksend and the reference implementation needs to be super stable during this period of time. Once we have the mobile wallets done (which should have Darksend and InstantX support) we can move back to improving Darksend.

So now that both mobile wallets have been implemented, why hasn't the working Masternode Blinding been implemented into DASH? Why is it still taking 20+ hours to send a simple anon tx with DASH Huh

??

Can we get an update from the DASH team about the ETA for Masternode Blinding? DASH mixing is horribly slow and unuseable. Thanks.

SO based on those posts/screencaps, Evan gave his own DASH community false hope and in fact if you look back on it, it was just hype that Masternode Blinding was "fast" and "working".

This entire history reminds me of an episode of American Greed.

Evan said: "Darksend should be lightning fast now" and a user 1 week ago posts it take 20 hours to mix some Dash using DarkSend?