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
Currently, following the development under the #112 branch, we are adding two fields to the Validator struct for the staking module: EthereumAddress and OrchestratorAddress.
We will need to update the functionality and also add tests to support the new changes, check for the conditions defined below and also create new tests suits that would check for the following:
When creating a new validator
The provided Orchestrator address is valid and not a duplicate (no previous validator uses the same orchestrator address)
The provided Ethereum address is valid and not a duplicate (no previous validator uses the same Ethereum address)
The provided Ethereum address is not the zero address
When editing a validator
Same as the previous
The text was updated successfully, but these errors were encountered:
rach-id
changed the title
Add functionality/tests to the newly added orchestrator/Ethereum addresses to the staking module
Add cheks/tests to the newly added orchestrator/Ethereum addresses to the staking module
Apr 13, 2022
adlerjohn
changed the title
Add cheks/tests to the newly added orchestrator/Ethereum addresses to the staking module
Add checks/tests to the newly added orchestrator/Ethereum addresses to the staking module
Apr 13, 2022
Currently, following the development under the #112 branch, we are adding two fields to the Validator struct for the staking module:
EthereumAddress
andOrchestratorAddress
.We will need to update the functionality and also add tests to support the new changes, check for the conditions defined below and also create new tests suits that would check for the following:
When creating a new validator
When editing a validator
The text was updated successfully, but these errors were encountered: