TrenchClaw: what we found
RPC read tool can't fetch version 1 transactions (maxSupportedTransactionVersion locked to 0).
Public since 2026-10-28. GitHub issue henryoman/TrenchClaw/issues/28 was posted.
Code: henryoman/TrenchClaw, their default branch on 2026-10-28. Reported to them: henryoman/TrenchClaw/issues/28.
Status: Open: no fix merged yet
Findings
breaks accuracy
RPC read tool can't fetch version 1 transactions (maxSupportedTransactionVersion locked to 0)
In apps/trenchclaw/src/tools/rpc/read.ts (line 384) the input schema is maxSupportedTransactionVersion: z.number().int().min(0).max(0).default(0), and apps/trenchclaw/src/solana/lib/rpc/getTransaction.ts (line 47) defaults it to 0. So the agent can't look up a version 1 transaction even when it asks for one: the RPC answers error -32015 ("Transaction version (1) is not supported by the requesting client").
Version 1 transactions are common on mainnet now (around 40% of non-vote transactions in a block I sampled), so a lot of lookups the agent makes will fail. Reproduced on mainnet on 2026-10-28:
apps/trenchclaw/src/tools/rpc/read.ts:384apps/trenchclaw/src/solana/lib/rpc/getTransaction.ts:47scripts/manualTestRpcReads.ts
getTransaction(<v1 signature>, { maxSupportedTransactionVersion: 0 }) -> error -32015
getTransaction(<v1 signature>, { maxSupportedTransactionVersion: 1 }) -> transaction (version 1)Fix: Allow and default to 1 (.max(1).default(1) in the schema, ?? 1 in getTransaction.ts). The tests and scripts/manualTestRpcReads.ts use 0 too.
What we measured
| What | Result | How | Checked |
|---|---|---|---|
| Reported to them | henryoman/TrenchClaw/issues/28, posted 2026-10-28 | https://github.com/henryoman/TrenchClaw/issues/28 | Oct 28, 2026, 2:30 AM UTC |
| Status | Open: no fix merged yet | GitHub issue henryoman/TrenchClaw#28 | Oct 31, 2026, 1:55 AM 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.