oasisprotocol / oasisprotocol/oasis-core
Nodes could cache received checkpoints even when not checkpointing
Open
Nobody has claimed this yet.
c:storage
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Even when storage nodes are not checkpointing on their own, they could cache checkpoints that they used to sync.
They could even randomly decide to replicate some checkpoints for better availability.
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. First understand how storage nodes receive and sync checkpoints, then determine the intended caching and replication policy. Done should include an agreed design for when checkpoints are cached and how random replication improves availability.
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
- 25/100