paritytech / paritytech/host-rust-core
RFC: Account certifications
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 10
- Forks
- 3
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 148
Description
Raised in: #222 · @filvecchiato
Description
Any two accounts can be certified as commonly controlled. A certification is either public, verifiable by anyone, or private, verifiable only by an audience named when it is issued.
Motivation
Nothing in the protocol lets a user state that two of their accounts belong to the same entity. The Playground implements a proof-of-control flow by hand; the private case cannot be expressed at all.
Requirements
- Any two accounts can prove common control — that the same entity controls both.
- Public certifications are verifiable by anyone.
- Private certifications are verifiable only by a designated audience.
Tasks
- RFC document body
- Implementation — rust-core
- Implementation — hosts
- dotli
- Desktop
- iOS
- Android
- host-cli
Note: no RFC drafted yet.
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 with RFC #222 and the Playground's existing proof-of-control flow; the issue names no files or tests. Define the public and private certification protocol in the RFC, then coordinate the listed rust-core and host implementations for dotli, Desktop, iOS, Android, and host-cli before considering the work done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, swift
- Domain
- api, backend-api-design, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100