From 361e5322e41b045a67b160f6d0be107fad7de1a6 Mon Sep 17 00:00:00 2001 From: Tyera Eulberg Date: Thu, 10 Sep 2020 13:34:25 -0600 Subject: [PATCH] Update commitment options (#12171) --- docs/src/apps/jsonrpc-api.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/src/apps/jsonrpc-api.md b/docs/src/apps/jsonrpc-api.md index 4ba6d8f4d3..96ff7b5455 100644 --- a/docs/src/apps/jsonrpc-api.md +++ b/docs/src/apps/jsonrpc-api.md @@ -111,10 +111,11 @@ Requests can be sent in batches by sending an array of JSON-RPC request objects Solana nodes choose which bank state to query based on a commitment requirement set by the client. Clients may specify either: -- `"max"` - the node will query the most recent bank confirmed by the cluster as having reached `MAX_LOCKOUT_HISTORY` confirmations -- `"root"` - the node will query the most recent bank having reached `MAX_LOCKOUT_HISTORY` confirmations on this node -- `"single"` - the node will query the most recent bank having reached 1 confirmation -- `"recent"` - the node will query its most recent bank +- `"max"` - the node will query the most recent bank confirmed by the cluster as having reached maximum lockout. +- `"root"` - the node will query the most recent bank having reached maximum lockout on this node. +- `"single"` - the node will query the most recent bank having reached 1 cluster confirmation. +- `"singleGossip"` - the node will query the most recent bank having reached 1 cluster confirmation via gossip votes; may occur before or after `single`, depending on gossip traffic. +- `"recent"` - the node will query its most recent bank. The commitment parameter should be included as the last element in the `params` array: