paritytech / paritytech/host-rust-core

RFC: Post-W3F account and identity API surface

Open
#542 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

rfc
Dominant language
Swift
Stars
10
Forks
3
Avg merge
1d 10h
Merged PRs (30d)
148

Description

Raised in: #222 · @filvecchiato

Description

Four post-W3F additions to the account and identity surface, tracked one RFC each.

Tasks

  • RFC: Unified signWithAccount across product and legacy accounts
  • RFC: getPrimaryDotNsName
  • RFC: Account certifications
  • RFC: Freebie claim account IDs under product keys

Note: the dotNsIdentifier discussion in #222's comments is tracked by #492 and #486, not here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the originating issue #222 and the referenced discussions, including #492 and #486, to understand the account and identity API context. The issue proposes four separate RFCs—unified signing, primary Dot Names, certifications, and freebie-claim account IDs—so completion would require defining and documenting each agreed API surface.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
api, authentication
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.