A community for the latest discussions about the cutting edge of crypto design, it's culture and significant crypto news. Decentralize everything. Check out our [Community Guidelines](https://relevant.community/crypto/post/6122269e61d1cd005a877277/62427d3ed587ad005b647828)
53474 Members
We'll be adding more communities soon!
© 2020 Relevant Protocols Inc.
A community for the latest discussions about the cutting edge of crypto design, it's culture and significant crypto news. Decentralize everything. Check out our [Community Guidelines](https://relevant.community/crypto/post/6122269e61d1cd005a877277/62427d3ed587ad005b647828)
53474 Members
We'll be adding more communities soon!
© 2020 Relevant Protocols Inc.
Relevant
Hot
New
Spam
Relevant
Hot
New
Spam
1
2.8K
1
2.8K
"Currently, we limit the memory consumption of the EVM in two ways: a quadratic memory expansion cost and a de-facto call stack depth limit enforced with the EIP-150 “63/64 rule”. These mechanisms are reasonably effective at their desired goal, but are both needlessly complicated and inefficient, punishing regular users too much and DoS attackers too little. This post proposes some alternative designs that better meet the key goal of limiting EVM memory usage."
"Currently, we limit the memory consumption of the EVM in two ways: a quadratic memory expansion cost and a de-facto call stack depth limit enforced with the EIP-150 “63/64 rule”. These mechanisms are reasonably effective at their desired goal, but are both needlessly complicated and inefficient, punishing regular users too much and DoS attackers too little. This post proposes some alternative designs that better meet the key goal of limiting EVM memory usage."
Some low-ranking comments may have been hidden.
Some low-ranking comments may have been hidden.