oasisprotocol / oasisprotocol/oasis-core
Storage availability probes
Open
Nobody has claimed this yet.
c:security
c:storage
s:needs adr
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
We need to implement a storage availability probe mechanism. This requires several components:
- Nodes doing the actual probes (probably using the existing storage API). I believe other storage nodes should be included in making these probes as storage nodes may perform regular syncs anyway and they also have some of the state at hand.
- A mechanism to present proofs of misbehavior. It is hard to prove non-availability though as it could be transient, due to (localized) network issues, malicious nodes (e.g., probe nodes could just say that something wasn't available) etc. One way is for proofs to be submitted to consensus and then other nodes could provide counter-proofs. This requires deposits of some kind to disincentivize fake proofs and rewards for probing nodes.
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
No files, tests, or entry points are named. Start by locating the existing storage API and consensus mechanisms, then determine how probe nodes, misbehavior proofs, counter-proofs, deposits, and rewards would fit together; done requires an agreed design and implementation of the full mechanism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100