Nexus deposits now take more confirmations than they used to

The number of on-chain confirmations the market wants to see before a deposit shows up as spendable balance has drifted higher.

If you have been reading this notebook for a while you will already have run into the pattern of a market changing a small number in a config file and no one being told out loud. This is one of those changes. The counter you see on the deposit screen has crept up. The move is small in absolute terms and easy to miss on any given deposit. The effect on how you plan a first order is not small.

How it read before

The old deposit screen quoted a low number of confirmations and, more usefully, the balance you could spend appeared to move at the same speed as the counter. You could refresh once and see the deposit sitting on the first confirmation. You could refresh again a short while later and see the number bumped. Somewhere very early in the count the balance would go from grey to black and the checkout button would light up. The workflow assumed that the wait was measured in one or two of something, not a longer sequence.

Because the wait felt small, a habit built up around it. Readers would open the deposit page, send from a wallet, and immediately switch tabs to a listing they had been eyeing. By the time they came back the balance would already be live. The order and the deposit felt like they had happened in one motion. When the counter jumped from zero to one on refresh, they read it as the market saying yes.

How it reads now

The counter target is higher. The balance you can spend does not move until the counter has reached the new figure. In between, the wallet page carries a short line that reads roughly "seen, waiting" next to the deposit row. The row is there. The number is there. It just is not yet money you can spend. The visible change is quiet, and readers who developed the reflex of starting a cart while the counter was still climbing now find the checkout button greyed out.

The pattern applies to both of the coins the market supports. It is more noticeable on the slower of the two, because the wait between confirmations is longer and the elevated target makes each extra confirmation more visible on the clock.

Why this probably shifted

The most likely reading is a defence against chain reorganisations. When a deposit is credited early and a small block is then orphaned, the market has to unwind the credit or eat the loss. At the volumes a market like this handles, even rare reorgs add up. Raising the confirmation count is the cheapest possible insurance against that failure mode. It costs readers patience; it does not cost operators anything to configure.

A secondary reading is that operators wanted the deposit page to stop being ambiguous. Under the old counter, a deposit could feel done when the market did not yet consider it done, and the mismatch generated support tickets. Pushing the threshold higher aligned the visible counter with the moment the market was willing to commit to the balance.

What to change on your side

If you have been treating the deposit page as instant, stop. Send earlier than you think you need to and let the counter fill before you start filling a cart. If the cart page you land on now shows a countdown, that countdown does not pause for your deposit to confirm. It will run out and your cart will empty while you wait.

• Fund the wallet first, browse second. Reversing the two saves a cart every time.
• Do not refresh the deposit page every few seconds; the counter does not move faster because you are watching it.
• Do not conclude that your deposit is stuck when you have refreshed twice and the count has not moved. It has not been long enough.
• If the counter really has not moved for a long stretch, check the sending wallet fee and the mempool before writing to support.

The behaviour that used to work, which was to top up the wallet and start ordering at once, now stalls. If you write to support because the spend balance has not appeared and the counter is still short of the target, expect to be told to wait. If you find yourself writing to support only after the mistake, a stalled deposit is a good place to break that habit and read the wallet row twice before typing anything.

What this entry is not claiming

This entry is not claiming that the market is failing to credit deposits, that the deposit is at risk, or that any specific number of confirmations is now required. It is claiming that the count has moved up from what it used to be and that the timing of a first order has to move with it. The current addresses page is the place to check you are on the real deposit screen before you send anything. This entry says nothing about that; it only describes what happens after you are already on it.