Alerts · November 18, 2026 · 7 min read

Wallet alerts without false alarms

Most false wallet alerts are not decoder bugs. They are real transactions that failed, never landed, arrived twice, or were never meant to matter. Here is each cause with its fix.

Solana wallet alert false positives mostly come from transactions that are real but do not mean what the alert says: they failed, never landed, arrived twice, moved wrapped SOL, or carried dust. Fix them with a status on every alert, a dedupe key on the first signature, a few decoding rules, and a second message once the outcome is settled.

Why early alerts go wrong#

An alert built on raw transaction data fires on intent. The watcher sees a signed transfer and says "you received 5 SOL" before the cluster has run it. Most of the time that is true. The false alarms are the cases where the signed request and the final result part ways, plus a few cases where the request was never what it looked like.

None of these are exotic. They show up on any busy wallet within days, and users stop trusting a bot after the second wrong message.

The catalogue: cause, symptom, fix#

CauseWhat the user seesFix
The transaction landed but failed"Received 5 SOL", then the balance never movesSend the early alert as "incoming, not settled", then confirm or retract after the outcome
The transaction never landed (expired, or its slot was skipped)An alert for money that never arrivesRetract once the blockhash has expired at finalized commitment and a second status check still finds nothing
The same transaction reached the watcher twiceTwo identical alertsKey alerts by the first signature and send once per key
Wrapped SOL movementsA token alert and a SOL alert for one action, or an alert for "WSOL" the user does not recogniseRecognise the native mint and the SyncNative and CloseAccount steps, and report the net SOL effect once
Dust and look-alike transfersA tiny transfer from an address that resembles a known oneSet a minimum amount per asset and flag senders the user has never transacted with
Account creation that moves lamports"Sent 0.002 SOL" when the user only opened a token accountClassify CreateAccount and token account setup separately from payments
Token-2022 transfer feesThe alert shows the amount sent, the user receives lessFor Token-2022 mints with a fee, read the fee field or say "before fees"
Self transfers between the user's own accountsAn alert for moving money from one pocket to anotherLet users group their addresses and skip internal moves

Two step alerts: early, then settled#

The single change that removes most complaints is splitting one alert into two messages:

  1. Early: sent as soon as the decoder sees the transfer. Worded as pending: "Incoming 5 SOL from the sender address, not settled yet."
  2. Settled: sent, or the first message edited, once the transaction's status is known from RPC. Either "Settled" or "Did not go through".

Store the alert with a status that only moves forward, the same model as in provisional rows. A background job checks open alerts with the getSignatureStatuses RPC method, which accepts up to 256 signatures per call, and closes them. Alerts still open after the transaction's blockhash has expired are marked as dropped.

Users who only want certainty can switch the early message off and receive the settled one alone. That choice belongs to them, not to the bot.

Dedupe that survives reconnects#

A receiver that restarts, a second feed for redundancy, or the same transaction in two forks can all deliver one transaction twice. In-memory dedupe forgets across restarts, so keep the record of sent alerts in storage, keyed by the first signature plus the watched address. The deduplication guide explains how long that record needs to live and why the same signature can legitimately appear in two forks.

What the alert message should say#

  • The asset and amount, with the mint for tokens, so a fake token with a familiar name is easy to spot.
  • The counterparty address in full or with enough characters to compare, never shortened to four characters.
  • The status in plain words: pending, settled, or did not go through.
  • For Token-2022 mints with a transfer fee, whether the amount is before or after fees.

Parsing these correctly is decoder work. The recipes for SOL transfers and token transfers show how the amounts and accounts are read, and SPL Token instructions explains why Transfer and TransferChecked carry different fields. Landed but failed covers why a transaction in a block can still have done nothing.

When an early alert is not worth sending#

If a wrong alert costs more than a late one, for example when the alert triggers a payout or a shipment, send only settled alerts. Early alerts also cannot catch everything: transfers that happen inside another program's call, such as a swap paying out to the user, are inner instructions and only show in the transaction's metadata after it runs. A watcher on raw data sees the swap request, not the payout.

Next steps#

Put the catalogue into tests before users find the cases for you. To run a watcher on live traffic, Standard Shreds delivers the raw stream your bot decodes.

Three neighbouring topics: spotting accounts as they are created helps separate a first deposit from a known wallet, a webhook may be all an alert needs if it only fires on confirmed data, and the Token-2022 notes explain transfers that arrive smaller than they were sent.

Sources#

Raw shreds on your own server

Ultra Low Latency Shreds is $200 and Standard Shreds is $100. You pay in crypto, tell us which IPv4 address and UDP port should receive the stream, and we wire it up by hand.

Read nextWhat decoding costs you in CPU, and how to measure it