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
In PR #8831, the UsingRegistryV2 contract provides various getters returning addresses for contracts comprising the Celo protocol. For each featured protocol contract, a constant pointer is defined and used to inform the corresponding getter. While this mechanism isn't too complex, duplicating this process in code for a particular contract can lead to errors.
The problem is that the EUR token has corresponding getters for its registry and exchange, while the BRL token does not. So retrieval of corresponding BRL contract address would require code that may be error prone and not follow the standard defined by the UsingRegistryV2 contract.
Consider defining within the UsingRegistryV2 contract getters corresponding to the BRL token.
Contract registry has no entry for
BRL
In PR #8831, the
UsingRegistryV2
contract provides various getters returning addresses for contracts comprising the Celo protocol. For each featured protocol contract, a constant pointer is defined and used to inform the corresponding getter. While this mechanism isn't too complex, duplicating this process in code for a particular contract can lead to errors.The problem is that the EUR token has corresponding getters for its registry and exchange, while the BRL token does not. So retrieval of corresponding BRL contract address would require code that may be error prone and not follow the standard defined by the
UsingRegistryV2
contract.Consider defining within the
UsingRegistryV2
contract getters corresponding to the BRL token.Part of the OpenZeppelin Release 6 Audit: @georgercarder @clarkhenry
The text was updated successfully, but these errors were encountered: