Skip to content

docs: document getSignatureStatuses searchTransactionHistory requirement#59

Open
gamandeepsingh wants to merge 1 commit into
solana-rpc:mainfrom
gamandeepsingh:docs/getsignaturestatuses-search-history-requirement
Open

docs: document getSignatureStatuses searchTransactionHistory requirement#59
gamandeepsingh wants to merge 1 commit into
solana-rpc:mainfrom
gamandeepsingh:docs/getsignaturestatuses-search-history-requirement

Conversation

@gamandeepsingh

Copy link
Copy Markdown
Contributor

Problem

Calling getSignatureStatuses with a real, indexed signature (confirmed
present in the signatures table) returns null:

{"jsonrpc":"2.0","id":1,"result":{"context":{"slot":...},"value":[null]}}

Adding {"searchTransactionHistory": true} as the second param returns
the full status correctly.

This matches standard Solana JSON-RPC semantics exactly (mainline
getSignatureStatuses also requires this flag to look beyond a
short-lived recent-status cache — see
crates/superbank-rpc/src/handlers/signatures.rs, where the
ClickHouse-backed historical lookup is skipped entirely unless
search_transaction_history is true). Not a bug, but it wasn't
obvious from crates/superbank-rpc/README.md's method list, so a new
integrator coming from a different RPC provider could reasonably
assume a signature known to exist would resolve without the flag.

Fix

Add a line to the notes in crates/superbank-rpc/README.md calling out
the searchTransactionHistory requirement next to the existing
getSignatureStatuses references.

Fixes #57

getSignatureStatuses only checks historical ClickHouse-backed status
data when the request sets searchTransactionHistory: true. Without it,
a signature already indexed in the signatures table still returns
null, matching mainline Solana JSON-RPC semantics but easy to miss
since it wasn't called out in the method list.

Fixes solana-rpc#57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

(docs): getSignatureStatuses should document searchTransactionHistory requirement

1 participant