-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
RPC API should operate on confirmed state only #2474
Milestone
Comments
mvines
added a commit
to mvines/solana
that referenced
this issue
Jan 18, 2019
…bled This commit should be reverted once solana-labs#2474 is fixed
solana-grimes
pushed a commit
that referenced
this issue
Jan 18, 2019
…bled This commit should be reverted once #2474 is fixed
solana-labs/example-tictactoe#57 is probably due to this too |
3 tasks
mvines
added a commit
to mvines/test
that referenced
this issue
Jun 12, 2020
…bled This commit should be reverted once solana-labs/solana#2474 is fixed
jstarry
referenced
this issue
in jstarry/solana
Aug 8, 2024
* SVM: examples: add paytube example * fix comment * fix tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the RPC API reflects the instantaneous state of the node. In the case of the leader's RPC API, this would be as soon as transactions are executed but not confirmed by the network. During leader rotation this can cause the appearance of a rollback to the RPC API user should a transaction be executed by the old leader but not confirmed by the cluster before the new leader takes over.
This behaviour can be observed fairly easily by running
USE_INSTALL=1 ci/localnet-sanity.sh -i 1000000
, which performsscript/wallet-sanity.sh
repeatedly on a local cluster as it rotates through leaders.Instead the RPC API for all nodes should probably only operate on the confirmed head of the ledger somehow.
Please revert 39b929c as a part of fixing this issue
The text was updated successfully, but these errors were encountered: