oasisprotocol / oasisprotocol/oasis-core
Expose `randomness` in SGX-RPC contract metadata
Open
Nobody has claimed this yet.
c:runtime/compute
p:3
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
If a particular contract function/method requires randomness from SGX,
libcontract should pass that in as an input parameter, similar to how we pass in state right now.
Contracts should not call sgx_rand directly
We want to do something using a common I/O interface
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 the SGX-RPC contract metadata path and the libcontract state input handling; no specific files or tests are named. Clarify the proposed common I/O interface and how randomness requirements should be represented, then define completion as contract methods receiving randomness without calling sgx_rand directly.
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
- 25/100