CrawlHive: what we found
CrawlHive reads other people's transactions with maxSupportedTransactionVersion: 0 in 13 places. Since 2026-09-15 a version 1 transaction read that way fails with RPC error -32015, so scans miss buys and a version 1 burn would not be credited. Nobody had been hit as of 2026-10-30.
Public since 2026-10-30. GitHub issue h100envy/crawl-hive#6 was posted.
Code: h100envy/crawl-hive, commit 72dd7ab5 (last public commit; development moved private on 2026-10-24). Reported to them: h100envy/crawl-hive/issues/6.
Findings
breaks accuracy
Sniper, first-buyer and bundle scans drop version 1 buys
Early buys are fetched with version 0 and failures become null (.catch(() => null)), so every version 1 buy is skipped without an error. A token can look cleaner than it is. In 2,201 sampled blocks from Oct 16-30, 55% of swaps on Pump.fun's bonding curve were version 1.
src/lib/server/scan-snipers.ts:114src/lib/server/scan-first-buyers.ts:120src/lib/server/scan-first-buyers.ts:152src/lib/server/scan-bundles.ts:79
Fix: maxSupportedTransactionVersion: 1 in these calls.
breaks money
Burn-to-pay would not credit a version 1 burn
The user's burn is read with version 0, so for a burn sent as version 1 the read throws on the first try and the confirm request errors out after the tokens are already burned.
src/lib/server/user-burns.ts:147src/lib/server/spawn-burn.ts:160
Fix: maxSupportedTransactionVersion: 1 in these calls.
breaks accuracy
Same read in seven more places
These also read transactions with version 0 and fail on version 1.
src/lib/server/tg-verify.ts:168src/lib/server/rewards.ts:227src/lib/server/buyback.ts:383src/lib/server/dexfund.ts:197src/lib/server/solana.ts:316src/lib/server/proof.ts:319src/components/proof-card.tsx:65
Fix: maxSupportedTransactionVersion: 1. @solana/web3.js is already ^1.99.0, the first 1.x that reads version 1, so nothing else changes.
Their addresses, read live
The newest transactions of each address, read from the chain when this page opened (refreshed at most every 5 minutes). A read that fails counts as unknown, never as a version.
| Address | Newest read | Version 1 | Version 0 | Legacy | Unknown | Latest activity |
|---|---|---|---|---|---|---|
| $CRAWLHIVE tokenD4jNDQ…wapump | reading… | reading… | reading… | reading… | reading… | reading… |
| BUYBACK_TREASURY (project treasury; spawn payments go here)DgCogt…rWTGUJ | reading… | reading… | reading… | reading… | reading… | reading… |
What we measured
| What | Result | How | Checked |
|---|---|---|---|
| $CRAWLHIVE transactions since burn-to-pay launched (Oct 21 18:20 UTC) | 1,743 successful: 415 version 1 (24%), 1,216 version 0, 112 legacy | Every signature for the mint, each read with getTransaction max version 1 | Oct 30, 2026, 10:38 PM UTC |
| Burns of $CRAWLHIVE in that window | 2, both version 0, both by BUYBACK_TREASURY. No user burned to pay, so no payment was lost. | spl-token burn/burnChecked instructions on the mint in those transactions | Oct 30, 2026, 10:38 PM UTC |
| Treasury income since Oct 10 | 71 transactions (55 legacy, 16 version 0, 0 version 1); 54 incoming, about 2.78 SOL and 11.12 USDC | Treasury wallet and its USDC account, every signature since 2026-10-10 | Oct 30, 2026, 10:45 PM UTC |
Proof you can repeat
5MRa9rSrdwN2Ys5eLqPG5rhXj73sw1tQ1iz5uG5nsEMKBmnY9aakLMHybH5c8WC35AGZTEa4pUxEppGN3atZCoyB (slot 463414568)
maxSupportedTransactionVersion: 0 → error -32015: Transaction version (1) is not supported by the requesting client
maxSupportedTransactionVersion: 1 → the transaction, version 1
checked Oct 30, 2026, 10:20 PM UTC
Tools run on this project
Check it yourself
Every Pulse tool, live on mainnet, starting with tx_version. Paste any signature from this report, or your own.
Toolbox
Pick any tool, change any input, run it on mainnet, and reopen any call to change it and run it again.
Ctrl ↵ runs the tool
Run when code can't find or read a transaction that is on chain, or before relying on code that reads other people's transactions. Read the docs
Response
Run the request to see the live response. The inputs are real mainnet data, so it works as it is.
Your calls 0
Calls you run appear here and stay in this browser. Open one to change its inputs and run it again.