caelum0x 33ba5c3475 fix: WalletProvider never subscribed to wallet accountsChanged/chainChanged
Eip1193Provider has always declared the standard on/removeListener event
hooks, but nothing in the app ever called them. Once connect() set
address/chain once, the UI kept using a stale address forever after the
user switched accounts or networks inside their wallet post-connect -
every subsequent vault/pool read and wallet-signed write kept targeting
the wrong account with no indication anything changed.

Wires accountsChanged (sync address, clear on wallet-side disconnect) and
chainChanged (drop the stale address + surface an error, forcing a
reconnect that re-validates the chain) through WalletProvider. Adds a
real regression test driving the actual component against a mock
EIP-1193 provider - confirmed it fails on the pre-fix code and passes
post-fix. First test suite for apps/web (vitest + jsdom + testing-library,
wired into the root test/lint scripts alongside core/cli).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-29 13:49:34 +03:00
..

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.