We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We already have ALLOWED_ADMINS env, which decides which addresses are allowed admins.
Managing those address (add/remove) is cumbersome, cause it needs a restart of the node. But we have accessLists, so :
ALLOWED_ADMINS
{ "1": ["0x123","0x124"], "2": ["0x345"] }
which means:
This way, node owner can use accessList contracts to define list of addresses.
Ocean-node will check both ALLOWED_ADMINS and ALLOWED_ADMINS_LIST (if they are defined) and if an address is a match on any , then it's allowed
ALLOWED_ADMINS_LIST
The text was updated successfully, but these errors were encountered:
paulo-ocean
No branches or pull requests
We already have ALLOWED_ADMINS env, which decides which addresses are allowed admins.
Managing those address (add/remove) is cumbersome, cause it needs a restart of the node. But we have accessLists, so :
ALLOWED_ADMINS
env variable, which looks likewhich means:
This way, node owner can use accessList contracts to define list of addresses.
Ocean-node will check both
ALLOWED_ADMINS
andALLOWED_ADMINS_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: