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

the quantus leg: deposit path spike, and the memo question raised with quantus and near #42

New Issue
Open
opened 2026-09-15 12:40:44 +00:00 by grenade · 0 comments
grenade commented 2026-09-15 12:40:44 +00:00
Owner
Copy Link

Parent: #7

Scope

Not buildable until Quantus is listed on Intents. Do the parts that are: (1) write to Quantus and NEAR with what the wallet needs from the bridge (one deposit address per quote or a shared one; if shared, how a deposit is attributed, since Quantus has no memo field; whether utility.batch with system.remark is acceptable); (2) implement the wallet side speculatively behind the registry gate: a non-reversible transfer_keep_alive to the deposit address, optional remark batch, tx hash to deposit/submit; (3) test it against a mock Intents that lists a Quantus asset on Heisenberg.

Record the answers as comments here; they are the spec for the real implementation.

Acceptance

The mock flow reaches SUCCESS from the wallet with a Heisenberg deposit. The written question and any answer are on this issue.

Depends on

Orders state machine; #22 (transfer).

Parent: #7 ## Scope Not buildable until Quantus is listed on Intents. Do the parts that are: (1) write to Quantus and NEAR with what the wallet needs from the bridge (one deposit address per quote or a shared one; if shared, how a deposit is attributed, since Quantus has no memo field; whether `utility.batch` with `system.remark` is acceptable); (2) implement the wallet side speculatively behind the registry gate: a non-reversible `transfer_keep_alive` to the deposit address, optional remark batch, tx hash to `deposit/submit`; (3) test it against a mock Intents that lists a Quantus asset on Heisenberg. Record the answers as comments here; they are the spec for the real implementation. ## Acceptance The mock flow reaches `SUCCESS` from the wallet with a Heisenberg deposit. The written question and any answer are on this issue. ## Depends on Orders state machine; #22 (transfer).
grenade added the child label 2026-09-15 12:41:53 +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#42
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?