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
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.
The text was updated successfully, but these errors were encountered:
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 inprivate.env
and the enclave proceeds as long as the whole url starts with one of the prefixes in the allowlist.The text was updated successfully, but these errors were encountered: