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.

Sign up for GitHub

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

Jump to bottom

StakeRegistry: fix inaccurate naming #173

Closed

wadealexc opened this issue Feb 6, 2024 · 0 comments

Labels

Collaborator

wadealexc commented Feb 6, 2024

From Dedaub audit, item A5:

The name of the function (and its argument) below is slightly misleading:
StakeRegistry::_validateOperatorStakeUpdateAtBlockNumber:445

function _validateOperatorStakeUpdateAtBlockNumber(
   	StakeUpdate memory operatorStakeUpdate,
    	uint32 blockNumber
) internal pure { … }

The function is used to validate StakeUpdate entries not just of the operatorStakeHistory mapping but also of the totalStakeHistory mapping.

wadealexc added the dedaub-audit label

wadealexc mentioned this issue

docs: fix grammer and inaccurate naming #179

Merged

wadealexc closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment