-
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
Staking router #463
Staking router #463
Conversation
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.
Slither found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.
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.
Tremendous changes 🙏
Leaving the first batch of comments to start with something.
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.
Here is the second batch 🙏
…b-tests Staking router/allocation lib tests
…de_operators_registry_tests
…s_registry_tests NodeOperatorsRegistry full unit tests coverage & fixes
fix: reward distribution array
…s_contract_size Reduce NodeOperatorsRegistry contract size
…posits-tests test: allocating between modules with different params
…on_fix fix: keys allocation fix
… into staking_router_external_params_to_uint256 # Conflicts: # contracts/0.8.9/StakingRouter.sol # contracts/0.8.9/interfaces/IStakingRouter.sol # contracts/0.8.9/test_helpers/StakingRouterMockForDepositSecurityModule.sol
…ms_to_uint256 Staking router external params to uint256
Staking Router post-audit fixes
The Lido protocol upgrade introduces the StakingRouter contract, that move towards a modular node operators registry architecture.