Knowledge Base · AI infrastructure
Wallet connect with two buttons: rebuilding it as a real modal
The symptom
Connecting a wallet meant reading a status string ('connecting…') and choosing between two hard-coded wallets. Users without either of them were stuck, and the interaction looked nothing like the rest of the interface.
What was actually wrong
The flow had been written as a phase check with inline markup rather than as a component. There was no wallet discovery, no chain information, and no way to add a provider without editing the layout.
The fix
A dedicated modal component: a blurred overlay, a grid of provider options that also lists wallets actually detected in the browser with a live indicator, a connected state showing the address and the active network, and payment actions per chain. Providers are registered through a wallet aggregator, so adding support for a new one is configuration rather than code.
What we took away
Wallet connection is the first interactive thing a visitor does; if it is a guess, nothing after it gets tried. Discovery beats enumeration — show what the visitor actually has installed.