You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -36,6 +37,8 @@ The full gRPC method definitions can be found in the [proto](../proto/README.md)
36
37
37
38
Returns a nullifier proof for each of the requested nullifiers.
38
39
40
+
**Limits:**`nullifier` (1000)
41
+
39
42
#### Error Handling
40
43
41
44
When nullifier checking fails, detailed error information is provided through gRPC status details. The following error codes may be returned:
@@ -73,10 +76,21 @@ authenticate the block's inclusion.
73
76
74
77
---
75
78
79
+
### GetLimits
80
+
81
+
Returns the query parameter limits configured for RPC endpoints.
82
+
83
+
This endpoint allows clients to discover the maximum number of items that can be requested in a single call for
84
+
various endpoints. The response contains a map of endpoint names to their parameter limits.
85
+
86
+
---
87
+
76
88
### GetNotesById
77
89
78
90
Returns a list of notes matching the provided note IDs.
79
91
92
+
**Limits:**`note_id` (100)
93
+
80
94
#### Error Handling
81
95
82
96
When note retrieval fails, detailed error information is provided through gRPC status details. The following error codes may be returned:
@@ -137,6 +151,8 @@ Clients should inspect both the gRPC status code and the detailed error code in
137
151
Returns nullifier synchronization data for a set of prefixes within a given block range. This method allows
138
152
clients to efficiently track nullifier creation by retrieving only the nullifiers produced between two blocks.
139
153
154
+
**Limits:**`nullifier` (1000)
155
+
140
156
Caller specifies the `prefix_len` (currently only 16), the list of prefix values (`nullifiers`), and the block
141
157
range (`from_start_block`, optional `to_end_block`). The response includes all matching nullifiers created within that
142
158
range, the last block included in the response (`block_num`), and the current chain tip (`chain_tip`).
@@ -181,6 +197,8 @@ When account vault synchronization fails, detailed error information is provided
181
197
182
198
Returns info which can be used by the client to sync up to the tip of chain for the notes they are interested in.
183
199
200
+
**Limits:**`note_tag` (1000)
201
+
184
202
Client specifies the `note_tags` they are interested in, and the block range from which to search for matching notes. The request will then return the next block containing any note matching the provided tags within the specified range.
185
203
186
204
The response includes each note's metadata and inclusion proof.
@@ -205,6 +223,8 @@ When note synchronization fails, detailed error information is provided through
205
223
Returns info which can be used by the client to sync up to the latest state of the chain for the objects (accounts and
206
224
notes) the client is interested in.
207
225
226
+
**Limits:**`account_id` (1000), `note_tag` (1000)
227
+
208
228
This request returns the next block containing requested data. It also returns `chain_tip` which is the latest block
209
229
number in the chain. Client is expected to repeat these requests in a loop until
210
230
`response.block_header.block_num == response.chain_tip`, at which point the client is fully synchronized with the chain.
0 commit comments