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
As per the usage template for the bridge it was found that the bridge validators list does not contains lots of validators. 3-7 is enough. Bigger number of validators is more difficult to manage and coordinate.
But initially, an assumption that the list could be huge was made. That's why to keep the list it was suggested to use the mapping that has more advantage for large lists (BaseBridgeValidators.sol and BaseRewardAddressList.sol) . But for the small lists expenses required for the SSTORE operations used in the mapping are higher. That's why later (BaseMediatorFeeManager.sol), the array started using instead of the mapping.
In order to keep consistency, consider to refactor the code to use the array in BaseBridgeValidators.sol and BaseRewardAddressList.sol modules.
The text was updated successfully, but these errors were encountered:
As per the usage template for the bridge it was found that the bridge validators list does not contains lots of validators. 3-7 is enough. Bigger number of validators is more difficult to manage and coordinate.
But initially, an assumption that the list could be huge was made. That's why to keep the list it was suggested to use the mapping that has more advantage for large lists (BaseBridgeValidators.sol and BaseRewardAddressList.sol) . But for the small lists expenses required for the SSTORE operations used in the mapping are higher. That's why later (BaseMediatorFeeManager.sol), the array started using instead of the mapping.
In order to keep consistency, consider to refactor the code to use the array in BaseBridgeValidators.sol and BaseRewardAddressList.sol modules.
The text was updated successfully, but these errors were encountered: