blackbeard/wallet
1
0
Fork 0
Code Issues 27 Pull Requests Actions Packages Projects Releases 4 Wiki Activity

taker flow in the wallet: buy qtc with btc, sell qtc for btc, through the escrow provider #61

New Issue
Open
opened 2026-09-15 14:41:57 +00:00 by grenade · 0 comments
grenade commented 2026-09-15 14:41:57 +00:00
Owner
Copy Link

Parent: #54

Scope

A second SwapProvider beside NEAR Intents, escrow, and the screens for it. The wallet stays PQ-only: it never holds a Bitcoin key.

  • Buy QTC with BTC: pick an offer, see the multisig address and confirm its derivation locally, watch the maker fund it and propose the refund, then show the BTC address and exact amount to pay from an external Bitcoin wallet (QR and copy), watch confirmations, propose release from the wallet's QTC key, and watch the maker's approval land.
  • Sell QTC for BTC: enter and confirm a BTC receive address (checksum validated, shown once more in the review screen), fund the escrow and propose the refund in one reviewed signing session, wait for the buyer's BTC, then approve and execute the release.
  • Every state of the trade is shown with what happens next and who has to act; the review screen for each signing step is decoded by Rust from the call bytes (#28's rule), including the fee leg of the release.
  • Orders persist and resume (#39's state machine gains the escrow states).

Acceptance

The epic's definition of done, driven from these screens on Planck plus signet.

Depends on

The protocol document; the coordinator; #28 (send with Rust-decoded review); #39 (orders state machine).

Parent: #54 ## Scope A second `SwapProvider` beside NEAR Intents, `escrow`, and the screens for it. The wallet stays PQ-only: it never holds a Bitcoin key. - **Buy QTC with BTC**: pick an offer, see the multisig address and confirm its derivation locally, watch the maker fund it and propose the refund, then show the BTC address and exact amount to pay from an external Bitcoin wallet (QR and copy), watch confirmations, propose release from the wallet's QTC key, and watch the maker's approval land. - **Sell QTC for BTC**: enter and confirm a BTC receive address (checksum validated, shown once more in the review screen), fund the escrow and propose the refund in one reviewed signing session, wait for the buyer's BTC, then approve and execute the release. - Every state of the trade is shown with what happens next and who has to act; the review screen for each signing step is decoded by Rust from the call bytes (#28's rule), including the fee leg of the release. - Orders persist and resume (#39's state machine gains the escrow states). ## Acceptance The epic's definition of done, driven from these screens on Planck plus signet. ## Depends on The protocol document; the coordinator; #28 (send with Rust-decoded review); #39 (orders state machine).
grenade added the child label 2026-09-15 14:42:22 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
child
One independently mergeable, verifiable step of an epic
 epic
A goal with an external definition of done; decomposes into child issues in dependency order
No Label child
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
grenade
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: blackbeard/wallet#61
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?