* RPC: use finalized as default pubsub commitment level (#16659)
* RPC: use finalized as default pubsub commitment level
* update docs
* Fix tests
(cherry picked from commit a7e65c0034
)
# Conflicts:
# core/tests/rpc.rs
* fix conflicts
Co-authored-by: Justin Starry <justin@solana.com>
This commit is contained in:
@@ -3147,7 +3147,7 @@ After connecting to the RPC PubSub websocket at `ws://<ADDRESS>/`:
|
||||
|
||||
- Submit subscription requests to the websocket using the methods below
|
||||
- Multiple subscriptions may be active at once
|
||||
- Many subscriptions take the optional [`commitment` parameter](jsonrpc-api.md#configuring-state-commitment), defining how finalized a change should be to trigger a notification. For subscriptions, if commitment is unspecified, the default value is `"confirmed"`.
|
||||
- Many subscriptions take the optional [`commitment` parameter](jsonrpc-api.md#configuring-state-commitment), defining how finalized a change should be to trigger a notification. For subscriptions, if commitment is unspecified, the default value is `"finalized"`.
|
||||
|
||||
### accountSubscribe
|
||||
|
||||
|
Reference in New Issue
Block a user