Problem
Wallet users cannot choose which TokenHolding an AMM action uses as its input or output.
When a wallet owns multiple TokenHoldings for the same token definition, the UI picks one implicitly or cannot continue. Output flows also do not let users choose between an existing TokenHolding and a new one.
Expected behavior
- Inputs show no-funds state when none match, select the only match automatically, and ask the user when several match.
- Outputs always let the user choose an existing matching TokenHolding or create a new one.
- Selection is based on program account type and decoded account state so the wallet can reuse it for other program account types.
Problem
Wallet users cannot choose which TokenHolding an AMM action uses as its input or output.
When a wallet owns multiple TokenHoldings for the same token definition, the UI picks one implicitly or cannot continue. Output flows also do not let users choose between an existing TokenHolding and a new one.
Expected behavior