oasisprotocol / oasisprotocol/oasis-core
Ephemeral runtimes
Open
Nobody has claimed this yet.
s:needs adr
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Features
- Cheap.
- Are created, same as any other runtime, but maybe with additional configuration.
- Some results are then communicated back to a different runtime.
- Are then terminated after a while (depending on per-runtime policy) and garbage-collected.
Use cases
- Game sessions where a possibly expensive game is played (mostly) off-chain, verifiably through TEEs. The final results are communicated back.
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
The issue names no files, tests, or entry points. Start by mapping runtime creation, result communication, termination, and garbage collection in the repository. Done would require an agreed design and implementation for ephemeral runtimes, but the issue does not define those details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100