-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix: adds proper handling for permissionless bold chains #45
base: main
Are you sure you want to change the base?
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.
Thanks @douglance !
Only one small (but needed) change 🙏
packages/assertion-monitor/index.ts
Outdated
) | ||
|
||
// Check validation permissioning based on chain type | ||
const validationPermissioningIssue = isBold |
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.
For BoLD you also have to check if the whitelist is disabled. It's normal to have a low baseStake if the chain is permissioned, but not normal if it's permissionless.
So the check should be something like validatorWhitelistIsDisabled && isBaseStakeBelowThreshold
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.
I think the issue is still present, where the base stake threshold is considered for permissioned chains too 🙏
parentClient, | ||
childChainInfo.ethBridge.rollup | ||
) | ||
const isBaseStakeBelowThreshold = await fetchIsBaseStakeBelowThreshold( |
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.
I think this checks now both BoLD and classic chains. This is not really needed for classic chains, but if you want to have the complete information, then we should change the comment in fetchIsBaseStakeBelowThreshold
, since it assumes it's a BoLD-enabled chain. Otherwise, restrict it only for BoLD chains.
alerts.push(VALIDATOR_WHITELIST_DISABLED_ALERT) | ||
} | ||
|
||
if (isBaseStakeBelowThresholdOnBold) { |
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.
I think the same thing still happens here, since it's not checking if the validator whitelist is disabled AND the baseStake is below the threshold 😅
No description provided.