EOS Bug Can Steal Your Ram, Price Up 5%

EOS Bug Can Steal Your Ram, Price Up 5%

EOS is up 5% today from about $4.9 to a recent high of $5.3 with it currently settling at $5.1 on reasonable trading volumes of about half a billion.

That’s after a new bug was revealed that can allow individuals to steal someone’s ram which is needed in EOS in order to make transactions. The bug report says:

“A malicious user can install code on their account which will allow them to insert rows in the name of another account sending them tokens.

This lets them steal RAM by inserting large amounts of garbage into rows when dapps/users send them tokens.”

They have come up with a temporary Proxy Token solution whereby you send the transaction to a proxy account which has no ram, they say:

“By sending tokens to a proxy account with no available RAM, and with a memo where the first word of the memo is the account you eventually want to send the tokens to, the only account they can assume database row permissions for is the proxy, which has no RAM.”

How many people will know of this temporary solution and how many will utilize it, remains to be seen, but eos’ price appears to be unaffected:

The market, thus, appears to not really care much of this bug or maybe they’re satisfied with the temporary solution, but another design problem in eos seems to be CPU.

You need a lot of it to play a game says a game developer. Detailing much of the cost, the apparent developer publicly said:

“10 EOS of CPU was burned in like a 30 minutes to an hour of play time. SO we started running the math to figure out how much she needs to be able to play the game. Umm guys, you need like 500 dollars of EOS staked into CPU to meet the minimum requirements to play EOS Knights on a constant basis.”

That’s in addition to ram, of course, and in addition to any amount you might want to spend on in-game items, making it a pretty expensive experience for eos dappers.

Copyrights Trustnodes.com

 

Share your thoughts, add a comment!

You must be logged in in order to place a comment.

Article comments

Loading...
No comments yet, be the first to comment this article