Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No RPC API to check that a transaction wasn't processed by a particular slot #27098

Closed
jstarry opened this issue Aug 12, 2022 · 0 comments
Closed
Labels
stale [bot only] Added to stale content; results in auto-close after a week.

Comments

@jstarry
Copy link
Member

jstarry commented Aug 12, 2022

Problem

To properly determine that a transaction has expired, it's necessary to check with an RPC node that the transaction hasn't been processed before a particular slot at a particular commitment level. This need arises from the fact that RPC nodes could be lagging far behind the block producer and may not have confirmed the last block that a transaction could have been processed in yet.

Unfortunately the getSignatureStatus and getTransaction API's aren't suitable for this type of query because getSignatureStatus can't be called with a commitment level and getTransaction doesn't return the context slot in which the request was evaluated.

Originally posted by @jstarry in #25839 (comment)

Proposed Solution

Introduce getTransactionStatus API which accepts a commitment parameter and returns a context wrapped response. This API will indicate whether a transaction was included in a block or not.

@github-actions github-actions bot added the stale [bot only] Added to stale content; results in auto-close after a week. label Aug 14, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale [bot only] Added to stale content; results in auto-close after a week.
Projects
None yet
Development

No branches or pull requests

1 participant