Your Solana WebSocket provider may be ignoring your filters
A cautionary result for anyone migrating Solana data providers, plus a method for proving a migration is lossless before you commit to it.
A cautionary result for anyone migrating Solana data providers, plus a method for proving a migration is lossless before you commit to it.
The short version
Some Solana RPC providers expose a WebSocket endpoint that accepts a transactionSubscribe request — returns a subscription id, streams data, no errors — while silently ignoring the account filters and the encoding parameter.
You do not get an error. You do not get an empty stream. You get a full firehose of every non-vote transaction on the network, in a different JSON shape than you asked for, billed by the byte.
If your consumer parses defensively it will quietly process nothing. If it doesn’t, it will crash on the first message. Either way the failure is silent at the transport layer, which is the worst place for a failure to be silent.