-
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
Feat/use only id externally #510
Feat/use only id externally #510
Conversation
582f7ef
to
36112d1
Compare
contracts/0.4.24/Lido.sol
Outdated
); | ||
(_getTotalPooledEther().mul(precisionPoints)) | ||
.sub(_totalRewards.mul(totalFee)) | ||
); |
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.
Why this formatting change? The result is much less readable.
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.
That change pertains to a former base branch, fix/typos-base-precision
which has already been merged to #482. This PR includes change only to StakingRouter and respective tests.
…ance/lido-dao into feat/use-only-id-externally
Could you please update the PR to resolve conflicts? |
…ance/lido-dao into feat/use-only-id-externally
Conflicts resolved. |
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.
lgtm, but it seems that storage read optimization is possible
This PR hides staking module indexes from the external interface. All external setters and getters use module ids now. Additionally, StakingRouter provides a getter for all module ids.