This repository was archived by the owner on Mar 11, 2025. It is now read-only.
Remove unconditional hidden commitment override for sanity #1528
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, sendTransaction via spl-token is confirmed with
recent
, even if the connection's confirmation isconfirmed
for example.This means any token transaction async executions could return too early, causing very hard-to-debug issues:
The following harmless-looking code doesn't work for some time:
Also, actually, we're seeing very confusing errors on the wild.
Last and not least, our partners are silently using
recent
for tx confirmation, this is too dangerous imo.solution
just use connection's configured commitment value.
I looked around git history maybe solana-labs/solana#12498 is the reason of this? How about doing
recent
for example?could possibly affecting solana-labs/solana#15705