Deprecate commitment variants (#14797)
* Deprecate commitment variants * Add new CommitmentConfig builders * Add helpers to avoid allowing deprecated variants * Remove deprecated transaction-status code * Include new commitment variants in runtime commitment; allow deprecated as long as old variants persist * Remove deprecated banks code * Remove deprecated variants in core; allow deprecated in rpc/rpc-subscriptions for now * Heavier hand with rpc/rpc-subscription commitment * Remove deprecated variants from local-cluster * Remove deprecated variants from various tools * Remove deprecated variants from validator * Update docs * Remove deprecated client code * Add new variants to cli; remove deprecated variants as possible * Don't send new commitment variants to old clusters * Retain deprecated method in test_validator_saves_tower * Fix clippy matches! suggestion for BPF solana-sdk legacy compile test * Refactor node version check to handle commitment variants and transaction encoding * Hide deprecated variants from cli help * Add cli App comments
This commit is contained in:
@ -149,7 +149,7 @@ vote, and vote account pubkey responsible for the vote.
|
||||
|
||||
Together, the transaction merkle and optimistic confirmation proofs can be
|
||||
provided over RPC to subscribers by extending the existing signature
|
||||
subscrption logic. Clients who subscribe to the "SingleGossip" confirmation
|
||||
subscrption logic. Clients who subscribe to the "Confirmed" confirmation
|
||||
level are already notified when optimistic confirmation is detected, a flag
|
||||
can be provided to signal the two proofs above should also be returned.
|
||||
|
||||
|
Reference in New Issue
Block a user