oasisprotocol / oasisprotocol/oasis-core
Support remote RONL components
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Currently hosting ROFL components implies that the RONL component is also available locally. But this does not need to be the case as long as an authenticated EnclaveRPC session can be established. We should add support for configuring a remote RONL endpoint (e.g. gRPC) which will be used instead of the local component.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how hosting a ROFL component currently locates and uses its local RONL component, then examine how an authenticated EnclaveRPC session is established. Define the configuration and connection path for a remote gRPC RONL endpoint, and verify that it is used instead of the local component when configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- blockchain, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100