You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Send dialog currently only has a "To" address field and amount. There is no way to specify:
A memo — needed for many dApps and services that use memos to identify deposits (e.g. exchanges, payment processors, canister-based services)
A subaccount — neither a source subaccount (for users who want to organize funds) nor a destination subaccount (for sending to ICRC-1 accounts with subaccounts)
This limits Oisy's usefulness for anything beyond simple peer-to-peer transfers.
Describe the solution you'd like
Add optional fields to the Send UI:
Memo field (bytes or numeric) — passed through to the ledger transfer call
Destination subaccount — the ICRC-1 textual representation already encodes subaccounts (principal + checksum + subaccount), but an explicit field would improve UX for users who receive a subaccount separately
These fields could be collapsed under an "Advanced" section to keep the default experience clean.
Additional context
The ICRC-1 standard supports both memo and subaccount in transfers — this is about exposing them in the wallet UI
Is your feature request related to a problem?
The Send dialog currently only has a "To" address field and amount. There is no way to specify:
This limits Oisy's usefulness for anything beyond simple peer-to-peer transfers.
Describe the solution you'd like
Add optional fields to the Send UI:
These fields could be collapsed under an "Advanced" section to keep the default experience clean.
Additional context
memoandsubaccountin transfers — this is about exposing them in the wallet UI