oasisprotocol / oasisprotocol/oasis-core
Support network I/O
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
For the TLSNotary application, we'll need to define an interface for supporting network I/O to and from the contract. One proposal is to specify certain methods to act as a callback function for network data, treating the network data as an input to the method call.
Because Ekiden contracts must be deterministic / RSM model, we want to treat these as inputs.
One potential reference is how we'll handle randomness:
#182
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 reading the TLSNotary and Ekiden context in the issue, then review the referenced randomness issue #182 for the proposed input-handling pattern. The issue does not name files, tests, or a concrete interface, so the expected implementation and completion criteria still need to be defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100