* Clarify the commitment levels based on questions
Many people have asked about what commitment levels mean, and which to
choose. This update includes some of the language at
`sdk/src/commitment_config.rs` and a recommendation for different use
cases.
Additionally, the preflight commitment documentation was out of date,
specifying that "max" was always used, and this is no longer the case.
* Update docs/src/developing/clients/jsonrpc-api.md
Co-authored-by: Tyera Eulberg <teulberg@gmail.com>
* Update docs/src/developing/clients/jsonrpc-api.md
Co-authored-by: Tyera Eulberg <teulberg@gmail.com>
* Update docs/src/developing/clients/jsonrpc-api.md
Co-authored-by: Tyera Eulberg <teulberg@gmail.com>
* Fix typo
Co-authored-by: Tyera Eulberg <teulberg@gmail.com>
(cherry picked from commit ede891a6c6)
Co-authored-by: Jon Cinque <jon.cinque@gmail.com>
* Update docs to show support for Nano X (#12647)
(cherry picked from commit 0ef3cac1f8)
# Conflicts:
# docs/src/wallet-guide/ledger-live.md
* Fix merge conflict
Co-authored-by: Dan Albert <dan@solana.com>
Co-authored-by: publish-docs.sh <maintainers@solana.com>
* Expose all rewards (fees, rent, voting and staking) in RPC getConfirmedBlock and the cli
(cherry picked from commit c5c8da1ac0)
# Conflicts:
# Cargo.lock
# runtime/src/bank.rs
# transaction-status/Cargo.toml
* fix: surface full block rewards type
(cherry picked from commit 1b16790325)
* resolve conflicts
Co-authored-by: Michael Vines <mvines@gmail.com>
* Record invoked instructions and store in transaction meta
* Enable cpi recording if transaction sender is some
* Rename invoked to innerInstructions
(cherry picked from commit 6601ec8f26)
Co-authored-by: Justin Starry <justin@solana.com>
* Fix 'Description will go into a meta tag in head' meta tag
(cherry picked from commit 5d682d2e05)
* Update index.js
(cherry picked from commit c231bb7154)
Co-authored-by: Michael Vines <mvines@gmail.com>
`--expected-shred-version` is another knob for users to get wrong and is
documentation that can get stale due to cluster restarts. Turns out
it's also generally not required anymore either because:
1. The cluster entrypoint can always be expected to be using the correct
shred version, and that shred version will be adopted by the new node
(earlier this was not the case when the `solana-gossip spy` node on
mainnet-beta.solana.com:8001 ran with shred version 0)
2. On a cluster restart, `--expected-bank-hash` is a much stronger
assertion that the validator is starting from the correct place (and
didn't exist when `--expected-shred-version` was first recommended)
(cherry picked from commit 4ada4d43f2)
Co-authored-by: Michael Vines <mvines@gmail.com>
* Add --restricted-repair-only-mode flag
(cherry picked from commit 63a67f415e)
* Add --gossip-validator argument
(cherry picked from commit daae638781)
* Documenet how to reduce validator port exposure
(cherry picked from commit c8f03c7f6d)
Co-authored-by: Michael Vines <mvines@gmail.com>
* Rpc: add getMultipleAccounts endpoint (#12005)
* Add rpc endpoint to return the state of multiple accounts from the same bank
* Add docs
* Review comments: Dedupe account code, default to base64, add max const
* Add get_multiple_accounts to rpc-client
(cherry picked from commit b22de369b7)
* Use new_response for consistency
Co-authored-by: Tyera Eulberg <teulberg@gmail.com>
Co-authored-by: Tyera Eulberg <tyera@solana.com>
