PROTOCOL: Self-Ejection For Nodes with Potentially Compromised Keys
Open
Nobody has claimed this yet.
flip: protocol
- Dominant language
- No language data
- Stars
- 26
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Contributor guide
No contributing guide indexed for this repository
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 protocol/20210118-self-ejection.md, the only project reference in the issue. Use it to determine the intended protocol change, affected assumptions, and acceptance criteria; the issue provides no files, tests, or completion criteria beyond the proposal link.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100