-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
LIP-6: burning the limited amount per single run [WIP] #389
Conversation
Make front-running exploits on `processLidoOracleReport` unprofitable by burning the limited amount only per single report.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 👌 Leave a comment about ability to set burn limit via constructor.
uint256 private maxBurnAmountPerRunBasePoints = 4; // 0.04% by default for the biggest `stETH:ETH` curve pool | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please consider to set the variable via constructor. It will save one extra call for setting via setter on deploy. 🙌
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll do it, an easy one 👍
Introduce new constructor param. Add tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 I've left just a couple of cosmetic remarks.
The token standard has the following direct note: > Callers MUST handle false from returns (bool success). Callers MUST NOT assume that false is never returned!
Remove reduntant requiremenets. Remove a revert reason from tests.
LIP-6: burning the limited amount per single run [WIP]
Make front-running exploits on
processLidoOracleReport
unprofitable by burning the limited amount only per single report.