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.
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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.batchwithsystem.remarkis acceptable); (2) implement the wallet side speculatively behind the registry gate: a non-reversibletransfer_keep_aliveto the deposit address, optional remark batch, tx hash todeposit/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
SUCCESSfrom the wallet with a Heisenberg deposit. The written question and any answer are on this issue.Depends on
Orders state machine; #22 (transfer).