Apparently a user attempting to explore (conceptually) a library managed (conceptually) accidental arbitrary execution on all users.
-
-
Show this thread
-
The flavor of that arbitrary execution was “Did your bank or wallet depend on our library? OK cool it’s gone.”
Show this thread -
I'm still trying to get my head around Ethereum, which I don't understand to Bitcoin levels, because my popcorn futures are undiversified.
Show this thread -
"So you're telling me that other people can do RPC against my financial infrastructure. Anonymously. And that's a good thing?"
Show this thread -
"It's like Bitcoin 2.0 if the main problem to be fixed was insufficient security-critical surface area and the solution was a new JavaScript VM."
Show this thread
End of conversation
New conversation -
-
-
Ethereum is not at fault here. It provides the platform on top of which Parity has released vulnerable software
-
But eth choose to do so while avoiding everything learned about secure coding in the last fifty years.
End of conversation
New conversation -
-
-
Not really accurate. The VM is bad and the language is bad but they are different bads.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
This Tweet is unavailable.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.