[RFC] Role Assignment Protocol and Registrar: Add Role Assignment Protocol For Nodes and Registrar
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 320
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 1
Description
Role Assignment Protocol and Registrar (RFC)
The Role Assignment Protocol acts as a decentralized or authority controlled way of assigning roles that can be verified to nodes. This protocol can be used to check on a Peers Assigned Role in the network and can be digitally signed by entities or use authority nodes to assign roles. These roles are modular and assigned by users.
Assigning Roles is useful as it means it will be easier to communicate with different nodes and more secure. The registrar can hold different registrations of nodes and can be done in a KAD with digital signatures in a decentralized manner.
It will sign a verified role and be viewable to the rest.
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
No files, tests, or entry points are identified. Start by clarifying the Role Assignment Protocol and registrar requirements, including KAD storage, authority or decentralized assignment, signatures, verification, and how roles are viewed by peers; done requires an agreed specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100