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

Hot swappable API #44

Open
amiller opened this issue Nov 10, 2024 · 0 comments
Open

Hot swappable API #44

amiller opened this issue Nov 10, 2024 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@amiller
Copy link
Contributor

amiller commented Nov 10, 2024

Right now, the API base URL is specified in teleport.env, with the API key passed in by the host (private.env).

This is because the choice of RPC providers does need to be constrained as part of the TCB. But, it's a little rigid because we can only have one.

Instead, what we should do is have a list of allowed RPC providers in teleport.env. Then the actual RPC+key can be provided in private.env and the enclave proceeds as long as the whole url starts with one of the prefixes in the allowlist.

@amiller amiller added enhancement New feature or request good first issue Good for newcomers labels Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant