You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
In commands/update_authority.ts the length of the command’s newValidators list is
checked in the following way:
if (newValidators.length < 1 || newValidators.length > MAX_NUM_VALIDATORS) {
throw new Error (
`newValidators length must be between 1 and ${ MAX_NUM_VALIDATORS }
(inclusive).` ,
);
}
Length check in updateAuthority
( lisk-sdk/framework/src/modules/poa/commands/update_authority.ts#33-37 )
Steps to reproduce
Check poa logic
Which version(s) does this affect? (Environment, OS, etc...)
v6.0.0
The text was updated successfully, but these errors were encountered:
Expected behavior
Schema validation should be used when available
Actual behavior
In two locations in the proof of authority module, checks are done manually when schema
validation could be used instead.
endpoint.ts
: the parameter given to getValidator is checked in the following way:Check in getValidator
( lisk-sdk/framework/src/modules/poa/endpoint.ts#33-37 )
In commands/update_authority.ts the length of the command’s newValidators list is
checked in the following way:
Length check in updateAuthority
( lisk-sdk/framework/src/modules/poa/commands/update_authority.ts#33-37 )
Steps to reproduce
Check poa logic
Which version(s) does this affect? (Environment, OS, etc...)
v6.0.0
The text was updated successfully, but these errors were encountered: