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
Copy file name to clipboardExpand all lines: basic-tutorials/api-key/customize-endpoint-advanced-features.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ If you require access to data from earlier blocks, you can utilize the **Archive
24
24
25
25
Enabling Archive mode will route all requests sent to this API key to the archive nodes of the blockchain network. It's important to note that there is a **30% increase in RU consumption**, since running an archive node requires significant storage capacity. 
26
26
27
-
In order to optimize efficiency, we recommend activating Archive mode only when necessary, or generate an individual API key to send the archive requests. Check [best-practices.md](best-practices.md"mention") to more efficiently use the feature. Additionally, processing times may be longer due to the substantial amount of data involved. Check [here ](../../build/supported-networks-and-advanced-features.md)for the full list of chains that the Archive mode is supported.
27
+
In order to optimize efficiency, we recommend activating Archive mode only when necessary, or generate an individual API key to send the archive requests. Check [best-practices.md](../best-practices.md"mention") to more efficiently use the feature. Additionally, processing times may be longer due to the substantial amount of data involved. Check [here ](../../build/supported-networks-and-advanced-features.md)for the full list of chains that the Archive mode is supported.
28
28
29
29
By default, the Archive mode is set to off. To enable it, simply click on the Archive mode symbol corresponding to the endpoint in the API Key list.
30
30
@@ -65,7 +65,6 @@ To use these functions, go to the Endpoint List of the user's dashboard, click t
65
65
66
66
<figure><imgsrc="../../.gitbook/assets/advanced features 2.png"alt=""><figcaption></figcaption></figure>
67
67
68
-
You are able to switch it to Normal, MEV Protection or Global Cast. Only one of the three can be selected.\
69
-
68
+
You are able to switch it to Normal, MEV Protection or Global Cast. Only one of the three can be selected.<br>
70
69
71
70
<figure><imgsrc="../../.gitbook/assets/advanced features 3.png"alt=""><figcaption></figcaption></figure>
Copy file name to clipboardExpand all lines: basic-tutorials/best-practices.md
+43Lines changed: 43 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -188,3 +188,46 @@ A batch call is a JSON-RPC method that bundles multiple requests (like `eth_call
188
188
In order to better serve different types of users and ensure the healthy and efficient operation of BlockPI RPC service network, we have implemented different restrictions on various types of endpoints. If a user triggers any of these restrictions, the system will return an error. The following table outlines these limitations:
189
189
190
190
<table><thead><tr><th>Endpoint Type</th><th width="388.3333333333333">Restrictions </th><th>Error Code</th></tr></thead><tbody><tr><td>Public</td><td>Not support WS/WSS</td><td>N/A</td></tr><tr><td>Public</td><td>Not support Debug_* and Trace_*</td><td>-32000</td></tr><tr><td>Public</td><td>Maximum request rate: 10 qps</td><td>429</td></tr><tr><td>Public</td><td>Maximum response body size: 3 MB</td><td>-32000</td></tr><tr><td>Public</td><td>Maximum block range: 1024</td><td>-32602</td></tr><tr><td>Public</td><td>Maximum batch size: 10</td><td>-32000</td></tr><tr><td>Private</td><td>Maximum block range: 5000 with address input</td><td>-32602</td></tr><tr><td>Private</td><td>Only support “callTracer” and ”prestateTracer” for debug method</td><td>-32000</td></tr><tr><td>Private HTTPS</td><td>Maximum batch size: 1000</td><td>-32000</td></tr><tr><td>Private WSS</td><td>Do not support batch call</td><td>-32000</td></tr><tr><td>All HTTPS</td><td>Do not support subscribe and filter rpc method</td><td>-32000</td></tr></tbody></table>
191
+
192
+
## Using gRPC in SUI SDK
193
+
194
+
The following is a sample code demonstrating how to use a **gRPC Endpoint** with the SUI SDK. Please note that we **do not support gRPC-Web**, only **native gRPC**.
195
+
196
+
```
197
+
import * as grpc from '@grpc/grpc-js';
198
+
import { SuiGrpcClient } from '@mysten/sui/grpc';
199
+
//import { GrpcWebFetchTransport } from '@protobuf-ts/grpcweb-transport';
200
+
import { GrpcTransport } from '@protobuf-ts/grpc-transport';
Copy file name to clipboardExpand all lines: build/api-reference/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ BlockPI Network is now fully available on more than **60 chains** including Main
15
15
16
16
BlockPI supports WebSocket and HTTPS. Note that the `eth_subscribe` method is only available for WebSocket. 
17
17
18
-
To safeguard the RPC node, every RPC provider sets a timeout for WebSocket connections to be disconnected periodically. In the case of BlockPI, the timeout is set to 30 minutes after each connection is established. Please check the code sample of our [best-practices.md](../../basic-tutorials/api-key/best-practices.md"mention") page for instruction.
18
+
To safeguard the RPC node, every RPC provider sets a timeout for WebSocket connections to be disconnected periodically. In the case of BlockPI, the timeout is set to 30 minutes after each connection is established. Please check the code sample of our [best-practices.md](../../basic-tutorials/best-practices.md"mention") page for instruction.
19
19
20
20
{% hint style="info" %}
21
21
If you send batch RPC requests in a single HTTPS request, cost would be based on the number of RPC requests. Note that there is limit time for a Https request. If too many RPC requests are sent with one Https request, there may be a timeout error. So the number is limited to 10 for public endpoints and 1000 for private endpoints.
0 commit comments