breaks money

payment-verify: Solana payments sent as version 1 transactions are reported as "transaction not found on chain"

verifySolana in src/payment-verify.js (line 194) calls getTransaction with maxSupportedTransactionVersion: 0 through the plain rpc() helper. For a payment sent as a version 1 transaction every RPC answers error -32015, so the loop ends with fail("transaction not found on chain (Transaction version (1) is not supported ...)") and a paid request is refused.

The history reads already handle this since yesterday's solana-history-rpc.js change (it re-asks with the version the node names), but payment-verify.js, src/solana-buyer.js (lines 127, 396) and src/solana-leaderboard.js (line 199) still make the version 0 call directly.

Version 1 transactions are a large share of mainnet now (about 40% of non-vote transactions in a block I sampled), so this depends only on which wallet or SDK the payer uses.

• src/payment-verify.js:194
• src/solana-buyer.js:127
• src/solana-buyer.js:396
• src/solana-leaderboard.js:199

getTransaction(<v1 signature>, { maxSupportedTransactionVersion: 0 })  -> error -32015 "Transaction version (1) is not supported by the requesting client"
getTransaction(<v1 signature>, { maxSupportedTransactionVersion: 1 })  -> the transaction (version 1, meta present)

Fix: maxSupportedTransactionVersion: 1 at those calls (the jsonParsed shape is the same for every version), or route them through solanaHistoryRead.