[y3v63n]

What this fixes

A delegator who stakes directly from a wallet sees 0 claimable rewards, even after their provider has distributed. The rewards are safe in the SplitsWarehouse, but the dashboard never reads the balance.

Why it happens

The dashboard resolves the warehouse address by calling SPLITS_WAREHOUSE() on one of the user's split contracts. It picked that split from token-vault delegations only:

const firstSplitContract = delegations[0]?.splitContract

A wallet delegator has no token-vault delegations, so the list is empty, the address is undefined, and the warehouse read stays disabled.

The change

Three commits, in order of what each one unblocks.

1. Show the balance — useAggregatedStakingData.ts

Fall back to a wallet delegation's split contract. Every split points at the same warehouse for a given token, so either source resolves the same address.

2. Let the user claim it — ClaimAllRewardsModal.tsx, plus prop threading

The claim-all modal resolves the warehouse the same way, and its withdraw step is gated on that address. Without this, the fix would show the amount, itemise it in the modal as "just needs withdrawal from warehouse", then add nothing to the cart on click, with no error.

The per-delegation path does not cover these users either: a fully distributed position has no rollup or split balance left, so the row reports zero rewards and its claim button is disabled.

3. Remove the duplication — resolveWarehouseSplit in claimCart.ts

The selection rule was written out at each call site, and the copies had drifted. Two looked at token-vault delegations only, which is what caused this bug. The rule now lives in one helper, called from the three sites that choose from a list. Each site keeps its own preference order.

The helper also scans for the first entry that carries a split contract, instead of reading index zero, so an entry without one no longer hides the warehouse from the entries behind it.

Scope

This affects any delegator who stakes only from a wallet, for any provider, after a distribution.

Token-vault delegators are unaffected. The wallet list is consulted only when no token-vault delegation supplies a split, so a user holding either or both kinds resolves the same address as before. The new props are optional with empty defaults.

Verified

Confirmed against a live case: a wallet with two wallet delegations, zero token-vault delegations, and 6,825.15 AZTEC unclaimed in the warehouse while the dashboard reported no rewards.

Type-check and lint pass on the changed files.

Not included

Per-row reward figures for wallet delegations still exclude the warehouse balance, so a fully distributed row reads zero and its button stays disabled. That balance belongs to the user and the token, not to one delegation, so attributing it per row would double count it across rows. The account-level withdraw above is the correct path, and it works after this change. A separate CTA next to the warehouse figure is worth a follow-up.

"Claim All Rewards" still claims only the warehouse balance for wallet delegations. Wallet rewards that are not distributed yet stay on the rollup or the split, so the modal total can be lower than the overview total. The "Claim All" button in the breakdown section already claims both delegation kinds. Queueing wallet claim and distribute legs from the modal is a follow-up.

🤖 Generated with Claude Code