Problem
The AMM UI's wallet view does not give users a useful account-level picture of
their wallet. Token definitions, holdings, program-owned accounts, creation
state, transaction feedback, and copy actions are fragmented or unavailable.
Reusable network, decoding, and portfolio behavior is also coupled to AMM
sources, while stale or failed reads can leave misleading presentation state.
Goal
Provide a shared wallet experience that presents account and token information
clearly, supports the wallet actions needed by the AMM UI, and exposes reusable
network, decoding, and portfolio services for other applications.
Proposed Scope
- improve shared wallet account state, creation flows, feedback, and copy
controls
- present token definitions and aggregate token holdings in the wallet view
- decode registered Token and AMM program accounts for display
- provide shared sequencer settings, identity verification, and portfolio
processing while leaving AMM deployment and token configuration app-owned
- cache verified token definitions and reuse current wallet snapshot account
reads where possible
- use canonical committed IDLs from
artifacts/ for the AMM UI resource bundle
- clear stale account presentation and treat failed account reads or decodes as
unavailable rather than presenting a zero balance
- add focused C++ and QML coverage for wallet presentation, network retries,
settings, decoding, cache behavior, and stale-refresh handling
Acceptance Criteria
- wallet shows readable token holdings and decoded program-account data
- account creation, copy, and transaction feedback remain usable in the shared
wallet controls
- account presentation is cleared or marked unavailable when its underlying
account read or decode fails
- stale sequencer probes and portfolio refreshes cannot overwrite newer state
- generic network, decoder, cache, and portfolio behavior is reusable outside
AMM sources
- AMM UI uses committed IDL artifacts rather than app-local duplicates
- focused wallet and AMM UI tests cover presentation, error, and cache behavior
Problem
The AMM UI's wallet view does not give users a useful account-level picture of
their wallet. Token definitions, holdings, program-owned accounts, creation
state, transaction feedback, and copy actions are fragmented or unavailable.
Reusable network, decoding, and portfolio behavior is also coupled to AMM
sources, while stale or failed reads can leave misleading presentation state.
Goal
Provide a shared wallet experience that presents account and token information
clearly, supports the wallet actions needed by the AMM UI, and exposes reusable
network, decoding, and portfolio services for other applications.
Proposed Scope
controls
processing while leaving AMM deployment and token configuration app-owned
reads where possible
artifacts/for the AMM UI resource bundleunavailable rather than presenting a zero balance
settings, decoding, cache behavior, and stale-refresh handling
Acceptance Criteria
wallet controls
account read or decode fails
AMM sources