Random not so random

My bags are already packed user.

Some pseudorandom collision thanks to shitty node.js coding doesn't affect the protocol.

>Are we going to have another DAO?

The obvious answer to that is, at some point yes.

So if he gets an big address he can dump it and the price might go to $50 or lower?

Pro tip: anyone mentioning the "DAO" right now is one of the Twitter FUDers.

Is that guy who hacked the addresses smarter than Vitalik Buterin?

Or is Romano actually Vitalik Buterin and did he build in the exploit just like the DAO to gain more profit?

almost impossible. kek

>Basically he got in someone's wallet and could took their ETH.

1. First they have to prove this. Based on his twitter account he could be full of shit.

>So it's more probable that there's something wrong with the random number generator

He used some fucking god knows what node.js to generate his wallet so if #1 is actually true there is a 99.99999% chance it's just some bogus node.js code.

The odds of this actually happening approach infinity.

Thirdly, ethereum allows additional layers of protection on top of the private keygen, which means that the actual protocol could be immune to even shitty third-party wallet generators in the future.

The DAO never happened?
I hate MSM news always lying.

Is this the rise of XRP finally

Yeah, I believe that idiot and his bullshit. He claims it was 'accidental'; what are the chances of that happening? Use your brain, OP (unless you're just shilling for a dump, in which case, go fuck yourself).

If this collision actually happened then we just witnessed one of the luckiest events that could possibly happen in multiple heat-deaths worth of time.
Far more likely however is that the implementation is broken or its fud shit.
Its probably fud shit.

The latter. It's been going on for hours. Same guy or group and piss easy to spot.

I'll finally have my 10k into Coinfloor tomorrow. C'mon chinks, crash ETH, reee!

Missed the whole drop this weekend cause of fucking exchange verification and transfer times. Finally want my ETH.

this is actually the worst FUDding I've ever seen on Veeky Forums

It's both extremely widespread and extremely low effort

My guess is it's a single person with a rotating proxy

This is the dumbest FUD ever. Even if it's true, all this means is that he's a lucky motherfucker for finding a collision or managed to generate the exact same address as some other guy. Good job selling it as a "hack" when you only need a superficial understanding of cryptography to tell it's not.

>generate the exact same address
generate the exact same private key*

Yeah, I did see the earlier thread with the Pandawhale twitter, so figured this guy was talking shit.

Zero points to OP for his faggy attempt.

I trust him, he's a developer of VIA which is a smaller coin, not a competition of ETH. Also he told multiple times before that he likes Ethereum and owns a big bag.

Yeah, you guys will call me a liar, I know, but what if I'm telling the truth? For me there's really only two options: "coincidence" or "the implementation is broken"

The wonders of turing completeness.

You can still dump your memecoin for bitcoin.

You forgot the third: you're a lying, FUDing piece of shit and everyone knows it.

Might as well stop at this point.

Believe it or not. Proof is on its way

I am reading his twitter and it looks like he is an ETH fanboy and Vitalik is his idol.

I think it is not his intention to damage Ethereum but I don't know maybe he is actually Vitalik Buterin and his nickname is Romano on Twitter.

Or the Dao hacker or all 3 are actually the same person it makes no sense at all.

What do I do?
Hold or sell my Ethereum?

you forgot the actual problem, the shitty third-party wallet generator he won't tell us the name of

>Somehow he managed to generate an ETH wallet's private key. Basically he got in someone's wallet and could took their ETH.
>It might ave been just a coincidence but the chance is so small that it's actually almost impossible. So it's more probable that there's something wrong with the random number generator. If it can be replicated than it's a really big problem for ETH.
A fucking tweet.

Fuck yourself, mate

sell all your crypto in general for falling for such a weak meme. God, I swear crypto is full of boomers trying to get in now.

/thread

I just tried to warn you guys to be careful. Didn't even tell you to sell. I'm out.

Who the fuck are you?
You fought in the Vietnam war?

GTFO pretending to be a badass crypto veteran.

>I am asking for advice so answer me polite!

In real life you gave me that attitude I probably pushed my private key up your ass.

Look at these fudders spreading their horseshit around like it fucking means anything

pastebin.com/fnVDJG2D

Here's the nodejs RNG. The bug must be in here or one of the functions calling it.

I am afraid with the DAO they gave warnings but nobody was listening.

Now there is an other exploit only now it is a multi billion market cap.

>I am really afraid and looking for advice and please provide arguments.

Not Fudd Shill Horseshit Weake meme and so on

Can someone confirm Romano is not Vitalik Buterin or The Dao hacker?
Is he still working for VIAcoin? Is it something worth looking at?

If this bug is for real, I think there's an upcoming hunting season for Ether wallets

wut

There is a bug in the nodejs RNG. It has nothing to do with ETH. Two people used a non-random wallet generator and came up with the same one. It's pretty simple.

Theres nothing in there pertaining to the actual RNG. Its just a data container. Where can I find the source for this? Ill comb through it

So everybody can generate random wallets with a balance?

How do I do that? If I get a wallet with 1000ETH best is to sell them for an other coin?

no, you can only generate existing wallets if you both used the same flawed RNG

don't use shitty nodejs code with poor entropy and bit length to make your wallet and you'll be fine

How many people used node.js-based tools? You never know

it uses openssl
either its being improperly seeded or this is fud shit

That's not ETH's or my problem. I always avoid nodejs like the plague for stupid shit like this.

it's likely the person who did this already knew about the state of the nodejs crypto RNG and bruteforced it for a long time

It's not ETH's problem per se, but it still will affect its reputation (and probably price as well) if there are tools that used node.js and a fair number of people that used those tools

openssl is in userspace, which means that its state is dependent on other components in the system and thus it's own use of /dev/urandom is meaningless outside of itself

Considering how many people jerk off to cloud computing, probably a lot

>The odds of this actually happening approach infinity.
You mean 1/inf?
user it doesn't matter how shitty the code was, if it generates a valid private key then there is either an issue or a statistical anomaly. Could certainly be a fluke but it could also be a serious issue with the ethereum vaporware

do you not understand?

This has nothing whatsoever to do with ethereum, in fact there have been wallet collisions in btc too

The problem is a shitty wallet generator with poor entropy. It's very likely that the via dev knew this and has been bruteforcing it for some time.

thanks senpai, just dumped my eth

you're an idiot

this is what happened - 2 guys, 1 piece of crappy wallet software that uses nodejs w/flawed random number generation

>step 1) first guy downloads crappy nodejs/pseudo-random wallet and creates an address
>step 2) second guy downloads the same crappy wallet, and it generates a duplicate address as the first guy because it's only pseudo-random

this has nothing to do with ETH. it's a shitty wallet program that's generating duplicate addresses. only people using this shitty program are at risk.

lol, when the articles about this will start popping tomorrow, FUD meme magic will happen, people will sell

let them, then I'll buy more cheap eth

which wallets use this? is myetherwallet affected? Is parity affected?

no idea, i only use official wallets

you mean mist? What about ledger wallets?

>halting problem
holy christ you're a tard

Gas.

Dont you idiots get it. WhalePanda is respected but it is known that he really hates ETH although he probably is holding a bag of more than a million usd of ETH.

Panic sell your stuff. Right now the only ones that spread this bs are the traders themselves but once some news normie posts this the price will drop, they will get a few extra and cash out in a few weeks when the prices hit a ath again

has this caused eth transfers to stall? had a pending transaction for an hour now, starting to get nervous

WhalePanda has your precious ETH now. Ask him nicely to give it back. He hates ETH anyway.

I've had ETH transactions stuck in limbo on Bittrex and Cuckbase for almost an hour. Dozens of confirmations on blockchain. WTF is going on.

i am making my ETH transactions just fine i just sold last night and i recieved today ETH i sent on tuesday morning to another wallet. Its from cuckbase but im reporting for anons not to belive the FUDers and faggot nocoiners. suck my balls, 45k gainz

Finally got my ETH deposit to show on cuckbase after 50 confirmations... Still nothing on Bittrex and there's 112 and counting. I picked a hell of a time to profit-take into BTC. I'm balls deep on ETH. No FUD intended. But something's fucky.

>WhalePanda is respected
hahahahahahAHHAHHHAHAHHAHAHAHHAHAHAHHAHHAH

Made this for the other thread. It's sad that people are falling for the only """true"" randomness is cryptographically secure. OpenSSL has been audited by both humans and programs that measure how random the data is.

It's going to be all fud and games till one day you wake up, check your eth wallet, see that it has 0 eth and a transaction to another account, then you go on Veeky Forums and see 30 other threads all with the same problem as you.

Or you wake up, find that ETH is worth $10 go on biz to see what happened, and see the 30 threads mentioned before

You don't seem to understand the problem. OpenSSL is only random within itself (it calls /dev/urandom directly), but NOT when it is called from another userspace program because it does not directly expose /dev/urandom to the program calling it. This is a stupid flaw that people have been trying to get them to fix for over a year.