Skip to content
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

Single stETH rebasing limit #428

Closed
TheDZhon opened this issue May 19, 2022 · 3 comments · Fixed by #514 or #482
Closed

Single stETH rebasing limit #428

TheDZhon opened this issue May 19, 2022 · 3 comments · Fixed by #514 or #482
Labels
next-upgrade Things to pickup for the next protocol upgrade

Comments

@TheDZhon
Copy link
Contributor

TheDZhon commented May 19, 2022

There is a discussion was introduced previously on the purpose of rebase-incurred sandwich-like arbitrageability: #405

The merge-ready protocol has separate limit enforcement levers to make these arbitrages unprofitable.
It was discussed on the Lido research forum that it's better to enforce the overall rebasing limit via a single number (and, effectively, using the single lever): https://research.lido.fi/t/announcement-merge-ready-protocol-service-pack/2184/8

The issue is here to pick up the idea while designing the next major protocol upgrade (I believe that it should be withdrawals-enabled protocol expected to happen with Capella or later)

@TheDZhon TheDZhon changed the title Single rebase limit Single stETH rebase limit May 19, 2022
@TheDZhon TheDZhon changed the title Single stETH rebase limit Single stETH rebasing limit May 19, 2022
@TheDZhon TheDZhon added the next-upgrade Things to pickup for the next protocol upgrade label May 19, 2022
@TheDZhon TheDZhon linked a pull request Jan 30, 2023 that will close this issue
@TheDZhon TheDZhon linked a pull request Jan 31, 2023 that will close this issue
@TheDZhon
Copy link
Contributor Author

Resolved in #482

@TheDZhon
Copy link
Contributor Author

TheDZhon commented Apr 6, 2023

Decided to re-open because V2 isn't deployed on mainnet yet.

@TheDZhon TheDZhon reopened this Apr 6, 2023
@TheDZhon
Copy link
Contributor Author

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
next-upgrade Things to pickup for the next protocol upgrade
Projects
None yet
2 participants
@TheDZhon and others