paritytech / paritytech/host-rust-core
Merchant Payment UX: High value transfers might want to await finalization
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 10
- Forks
- 3
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 148
Description
Raised here: https://github.com/paritytech/polkadot-android-community/issues/138
Currently the payments to external consumer (e.g. merchant payments) await the transfer before coins has been sent & claimed at the best block. In contrast, in-chat payments continue to monitor transactions up finalized state while also retrying them
Long-term solution
A general-purpose transaction history system. It should have two main responsibilities:
- Keep track of high-level payment operations and perform the retries in generic fashion - this should dedub case-by-case retry systems we have right now for claim and send
- Have a UI to report realtime statuses of each transaction (in the list form) to the user
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 the linked issue and compare the described external-consumer payment flow with the in-chat payment flow, especially finalization monitoring and retries. The long-term direction calls for a general transaction history system covering payment operations, generic retries, and realtime transaction statuses; the issue does not identify files, tests, or a narrower completion boundary.
Written by the indexing model from the issue text.
Assessment
- Domain
- payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100