paritytech / paritytech/host-rust-core

RFC: Unified signWithAccount across product and legacy accounts

Open
#543 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

signWithAccount accepts any AccountId the User Agent can attempt to sign with and that TrUAPI has returned into this product on this device. It replaces the *WithLegacyAccount variants of raw signing, payload signing and transaction construction.

Motivation

The signing surface is split by key provenance, so a product must know which kind of account it holds before it can pick a method.

Requirements

  • Accepts any AccountId the User Agent can attempt to sign with.
  • The account must have been returned by TrUAPI into the current product on the current device.
  • Covers raw signing, payload signing and transaction construction.

Tasks

  • RFC document body
  • Implementation — rust-core
  • Implementation — hosts
    • dotli
    • Desktop
    • iOS
    • Android
    • host-cli

Note: no RFC drafted yet.

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 with the originating issue #222 and the missing RFC document body. Define the unified signWithAccount surface for raw signing, payload signing, and transaction construction before examining the rust-core and host tasks for dotli, Desktop, iOS, Android, and host-cli. Done means the RFC is drafted and all listed implementations support the stated AccountId requirements.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, ios, rust, swift
Domain
api, cli, documentation, mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.