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
We already have AUTHORIZED_DECRYPTERS env, which decides which addresses are authorized to decrypt data.
Managing those address (add/remove) is cumbersome, cause it needs a restart of the node. But we have accessLists, so :
add AUTHORIZED_DECRYPTERS_LIST env variable, which looks like
{
"1": ["0x123","0x124"],
"2": ["0x345"]
}
which means:
for chainId 1 , call "balanceOf(ADDRESS_TO_CHECK)" on contracts 0x123 and 0x124
for chainId 2 , call "balanceOf(ADDRESS_TO_CHECK)" on contract 0x345
This way, node owner can use accessList contracts to define list of addresses.
Ocean-node will check both AUTHORIZED_DECRYPTERS and AUTHORIZED_DECRYPTERS_LIST (if they are defined) and if an address is a match on any , then it's allowed
The text was updated successfully, but these errors were encountered:
We already have AUTHORIZED_DECRYPTERS env, which decides which addresses are authorized to decrypt data.
Managing those address (add/remove) is cumbersome, cause it needs a restart of the node. But we have accessLists, so :
AUTHORIZED_DECRYPTERS_LIST
env variable, which looks likewhich means:
This way, node owner can use accessList contracts to define list of addresses.
Ocean-node will check both
AUTHORIZED_DECRYPTERS
andAUTHORIZED_DECRYPTERS_LIST
(if they are defined) and if an address is a match on any , then it's allowedThe text was updated successfully, but these errors were encountered: