Fix vault chain selection

[rossgalloway]

Problem

On the main vaults page, selecting a single chain could still show vaults from other chains.

This happened because the V2 and V3 vault filters skipped chain filtering for holdings, so connected-wallet positions on other chains leaked into the list. The page also had two different chain-selection behaviors: the top chain selector behaved like a single-select control, while row-level chain chips could build mixed selections. That mismatch could leave the page feeling stuck in a repeated updating state while switching chains.

Fix

• apply selected-chain matching uniformly in the V2 and V3 vault filters, including holdings
• extract a shared single-chain selection helper
• use that helper for both the top chain selector and row-level chain chips so chain switching follows one rule everywhere
• add focused tests for selected-chain matching and single-chain selection behavior

How To Review

1. Open the main vaults page with a wallet that has holdings on multiple chains.
2. Select a single chain from the top selector and confirm the list only shows vaults from that chain.
3. Click a row-level chain chip and confirm it switches directly to that chain rather than accumulating mixed chain selections.
4. Click the same active chain again and confirm it clears back to All Chains.
5. Spot-check both V2 and V3 views.

Testing

• bunx vitest run src/components/shared/hooks/useVaultFilterUtils.test.ts src/components/pages/vaults/utils/chainSelection.test.ts
• bun run tslint
• bun run lint:fix

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
yearnfi	Ready	Preview, Comment	Mar 18, 2026 9:07pm

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[0xeye]

LGTM