-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[AIP-33][Block Gas Limit] #132
Comments
@thepomeranian what kinds of DoS attacks does this introduce? Perhaps a malicious validator stuffs in a bunch of no-ops in a loop order to crowd out oracle updates? |
ddos attacks,,,,? |
A malicious validator can always propose empty blocks, so this AIP does not introduce new attack vector. |
At worst case, a malicious validator can pollute a single round of consensus in which they are the proposer. Per what @danielxiangzl said this introduces no new attack vectors. Because the validator would be just as good not proposing any transactions at all. |
top !! bravo le gars ! |
Ya, it was one of my quandary. But one thing that I fund is the gas is more descended since the first day. |
AIP-33 - Block Gas Limit
Summary
The per-block gas limit (or simply block gas limit) is a new feature that terminates block execution when the gas consumed by the committed prefix of transactions exceeds the block gas limit. This ensures that each block is executed within a predetermined limit of computational resources / time, thereby providing predictable latencies for latency-critical applications that involve even highly sequential and computationally heavy transactions.
Link to AIP: https://github.com/aptos-foundation/AIPs/blob/main/aips/aip-33.md
The text was updated successfully, but these errors were encountered: