Skip to content
New issue

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

Config env AUTHORIZED_DECRYPTERS_LIST #811

Open
alexcos20 opened this issue Jan 22, 2025 · 1 comment · May be fixed by #836
Open

Config env AUTHORIZED_DECRYPTERS_LIST #811

alexcos20 opened this issue Jan 22, 2025 · 1 comment · May be fixed by #836
Assignees
Labels
Type: Enhancement New feature or request

Comments

@alexcos20
Copy link
Member

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

@alexcos20 alexcos20 added the Type: Enhancement New feature or request label Jan 22, 2025
@paulo-ocean paulo-ocean linked a pull request Feb 5, 2025 that will close this issue
@giancu4
Copy link

giancu4 commented Feb 10, 2025

@jamiehewitt15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants