Two weeks ago I wrote about Solana RPC error -32015: if your code reads transactions with maxSupportedTransactionVersion: 0, every version 1 transaction fails with "Transaction version (1) is not supported by the requesting client", and your app silently skips it.
The headline number was "4 in 10 transactions". That's true, but a fair question came up: 4 in 10 of what? If those are a few bots spamming the chain, a wallet app or a payment tracker that can't read v1 loses very little. If they're ordinary people, it's a real bug for real users.
So I measured who sends them.
How I measured it
- 1,000 finalized mainnet blocks, spread from Nov 12 to Nov 16, 2026 (0 skipped slots, 0 failed reads)
-
getBlockwithtransactionDetails: "accounts"andmaxSupportedTransactionVersion: 1 - vote transactions left out
- sender = fee payer, the first account key (the wallet that signed and paid)
It ran as a Cloud Run job with 10 workers on the public RPC, and every block keeps its own blockTime, so anyone can re-check a slot.
What I found
| legacy | v0 | v1 | |
|---|---|---|---|
| Transactions | 93,034 | 119,028 | 153,864 |
| Different wallets sending them | 18,373 | 27,913 | 7,641 |
| Share sent by the busiest 100 wallets | 62.9% | 40.3% | 75.4% |
| Wallets with only 1-3 transactions in the sample | 17,024 | 24,570 | 6,854 |
Put plainly:
- v1 is 42.0% of non-vote transactions (153,864 of 365,926).
- But only 14.4% of wallets sent any (7,641 of 53,182). About 1 in 7.
- v1 is heavily concentrated. The busiest 100 v1 wallets sent three quarters of all v1. The busiest 10 sent a third. The top senders trade on Scorch, BisonFi and Pump.fun, thousands of times in the sample. That's bots.
- Real users are in there too. 6,854 wallets sent only 1-3 v1 transactions in the sample. They're only 5.4% of v1 volume, but they're the people whose deposits, payments and history go missing in an app that can't read v1.
- Only 379 wallets sent v1 and another version, so a wallet tends to stick to whatever its software builds.
What that means for your app
It depends on what you build:
- Trading tools, indexers, sniper and copy-trading bots, analytics: you're blind to most of the volume. If your bot watches "first buyers" or bundles on a new token, a big share of the real buys is invisible to it.
- Wallets, portfolio and tax tools, payment and deposit trackers: fewer users are hit, but the ones who are see a deposit that never arrives or a history with holes, and they get no error message, because the bug is silent.
Either way, it's a one-line fix.
The fix
// before: every v1 transaction throws -32015
connection.getTransaction(sig, { maxSupportedTransactionVersion: 0 });
// after
connection.getTransaction(sig, { maxSupportedTransactionVersion: 1 });
Same for getParsedTransaction, getBlock and getParsedBlock. And check your library version, because some versions throw on a v1 answer even when you ask for it:
| Library | Can read v1 |
|---|---|
| @solana/web3.js 1.95.8 to 1.98.4 |
No: throws even with maxSupportedTransactionVersion: 1
|
| @solana/web3.js 1.99.0+ | Yes |
| @solana/kit 7.1.0+ | Yes (earlier versions return the version as 1n and the types reject 1 before 6.10) |
| solana-py 0.30.2 to 0.41.0 | Yes, with the setting |
I tested each one against a real v1 transaction on mainnet.
To find the bug in your own code:
grep -rn "maxSupportedTransactionVersion" --include=*.ts --include=*.js --include=*.py . | grep ": *0"
Any hit is a place where v1 transactions disappear.
Caveats
- 1,000 blocks over 4 days is a sample, not a census. Treat the shares as approximate. In my earlier weekly samples the v1 share went from 0% until early September 2026 to about 45% since October.
- "Fee payer" is not always "the person": a relayer or an app can pay fees for its users. That would make v1 look more concentrated than it is, not less.
- "Busy wallet = bot" is my reading of thousands of transactions in 4 days, not something I checked wallet by wallet.
If you want to check a single transaction
My open-source tool Solana Pulse has a free tx_version check: give it a signature and it tells you the version and which settings and library versions can read it. You don't need it for the fix above.
If you maintain a Solana app and you're not sure whether you're affected, leave a comment with the library and version you use and I'll tell you what I found in testing.
Top comments (0)