Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Coin purses (RFC 17) in the Rust core

Open
#970 0 comments 0 reactions 2 assignees View on GitHub

Maintainers usually reply within 1 day

@TorstenStueber is already working on this.

Since Sep 24, 2026.

Assessment

This issue has not been assessed yet.

Description

Host Rust Core

Part of Coinage R3 (#968).

Goal

Products manage coins through purses: the RFC 17 CoinPayment API in truapi-server is backed by the Rust coinage implementation, with the CoinPayment permission and consent on both platforms. Existing coins already derive under RFC 17's main-purse path (//coinage//4294967295//…), so no re-keying is needed.

Open questions

  • RFC 17 has no durability guarantees yet: create_cheque, deposit and refund lack idempotency and a way to list or resume earlier attempts. It needs the same revision RFC 6 received.
  • Reinstall and backup recovery of purses (purse metadata, receive keys, in-flight operations) is not covered by RFC 17 and is a separate, large topic.
  • Other RFC 17 gaps: cheque encryption, the refund return path, and the clearing reference for payments made of several transactions.
  • Keeping purses separate may weaken recycling privacy.

Blocked by #969 (coinage port) and #965 (shared purse logic).

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

Getting set up

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.

More from paritytech/host-rust-core

All issues in paritytech/host-rust-core

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.