The Nexus market seems to keep a smaller balance cache

The balance on the wallet page seems to be cached shorter than it used to be, and refreshes less patiently when you open the page.

A balance page has to answer two questions at once. It has to show a number quickly so the page loads. It has to show the right number, which sometimes takes longer to fetch than the page load can afford. The way the market resolves that tension has changed a little. The old resolution favoured showing you what it showed last time. The new resolution favours showing you what is true now, even if that means a small delay.

How it read before

The old wallet page would open with the last balance it had for you and refresh in the background. The number would appear instantly. If the number was slightly out of date, it would quietly correct itself as you moved around the page. There was almost never a spinner. The user experience was of a page that always knew what it was talking about.

The cost of that experience was that, in a small number of edge cases, the number on the page was wrong for a beat. Readers occasionally reported that the balance jumped after they clicked to a listing and came back. The jump was the cache catching up. It was small and rare, but it existed.

How it reads now

The wallet page now shows a brief spinner in the balance area on load. The number lands a beat later than the rest of the page. Once it lands it holds still, but if you have just come off a deposit or a refund the number can move mid-view because the market itself is still resolving what it should be.

On mobile the effect is more visible because the page load is slower to begin with. The number is one of the last things to paint. Readers on the mobile view that stopped scaling the way it used to will notice the balance sliding into place after the rest of the layout has settled.

Why this probably shifted

The most likely reading is scale. As the market grew, cached balances that lagged the real state generated more support work and more disputes about what was really in the wallet at what time. A tighter refresh with a small delay is a cheaper solution than a chatty support inbox.

A related reading is that the balance page now has to reconcile more moving parts than it used to. Rotating deposit addresses, refunds resolving in a different coin, and a higher withdrawal floor all touch the same number. The cache has to know about all of that to be right, which is easier to do fresh than from memory.

What to change on your side

Read the number twice. Load the wallet page, wait a beat for the balance to land, and only then act on the number. If the number is the reason you are about to do something, do not act during the spinner.

• If the balance disappears for a second, do not panic; it is refreshing, not gone.
• If the number changes mid-view, do not conclude you were robbed; the market is reconciling a deposit or a refund.
• If the session logs you out sooner than it used to right in the middle of a balance refresh, sign back in and the number will settle again.
• If the balance is not what you expected and it has settled, the wallet page is the place to check; support cannot see anything you cannot see.

The pattern to break is reading the balance while the page is still loading and then acting on that reading. The cached number that used to sit there instantly was often right; the number that now flickers into place is more often right. Give the flicker a second.

What this entry is not claiming

This entry is not claiming the market is under strain, that balances are unreliable, or that the wallet page is broken. It is claiming that the balance display refreshes on a slightly less patient cadence and that the reading habit around it needs to adjust by a beat. If your balance is wrong after it has settled, that is a real question. If it moved during the spinner, that is not.