-
Notifications
You must be signed in to change notification settings - Fork 193
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
Deposits accounting #626
Merged
TheDZhon
merged 15 commits into
feature/shapella-upgrade-followups
from
fix/deposit-flow
Feb 20, 2023
Merged
Deposits accounting #626
TheDZhon
merged 15 commits into
feature/shapella-upgrade-followups
from
fix/deposit-flow
Feb 20, 2023
+953
−259
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
26 tasks
TheDZhon
approved these changes
Feb 20, 2023
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.
…ps' into fix/deposit-flow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Deposit accounting & contracts changes:
StakingRouter
now accepts the precise amount of deposits to make. IfStakingRouter
can't make the requested number of deposits, it will revert the transaction.StakingRouter
doesn't return ETH to theLido
contract after the deposit, so theLido.receiveStakingRouterDepositRemainder()
method was removed.StakingRouter.getStakingModuleMaxDepositsCount()
method signature changed. It now accepts two arguments:stakingModuleId
and the max amount of ether that might be deposited.IStakingModule.obtainDepositData()
now must return the exact number of requested keys. IfStakingModule
doesn't have enough deposit data items, it MUST revertIStakingModule.obtainDepositData()
now doesn't returndepositsCount
as the first item. OnlypublicKeys
andsignatures
returned nowAssertion that deposited correct amount of ETH was moved from the
BeaconChainDepositor
contract toStakingRouter
for clarityLido._markAsUnbuffered()
method was removed. Now, the buffered ether value is updated in place on deposit, like in other methods.Assert for unaccounted ether was removed from
Lido
. Previously such a check was relevant cause the deposits happened in theLido
contract itself. In the current implementation, ETH is sent toStakingRouter
, where deposits happen, which contains assert that exactly the received amount of ETH was deposited.Lido._getUnaccountedEther()
method was removedLido.getDepositableEther()
returns a value not multiple to 32 etherCheck that
stakingModuleId
is less thantype(uint24).max
was removed fromLido.deposit()
cause external interface of staking modules declares id asuint256