Can an evil contract fill users' ram with junk data?
3
-
1I think would be nice if EOS need support some kind like "ram limit"(similar gas limit on Ethereum) when submit a transaction to prevent malicious contract eat up all user's ram.– user1627Jun 28, 2018 at 10:22
-
I see the max_net_usage_words and max_cpu_usage_ms setting in the transaction, but no ram limit, I think your suggestion is great– Jimmy GuoJun 28, 2018 at 10:26
-
This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review– John WilliamsonJul 9, 2018 at 11:41
Add a comment
|
2 Answers
Yes, but it can only consume the ram of users who send it actions. Users should avoid sending actions to contracts which don't provide a way to release users' ram.
-
but many users don't review the code, they just use the dapp, I think @user1627's suggestion below is a good solution Jun 28, 2018 at 10:24
I am confused because you are asking questions without distinguishing between users and contract deployers.
If your question implies a contract deployer, it is to use the RAM of the account that deployed the contract.
RAM is purchased and used by contract writer(deployer), and it is entirely the contract writer's fault that they are misused within their limits.
Of course, it would be nice to provide a way to make sure your network can respond to these mistakes.