Liteservers
The service provides access to a Lite API for interaction with a liteserver node (opens in a new tab).
This API is used in applications that require access to low-level blockchain data (transactions, account states, etc.) and guarantees the reliability of this data (proof verification (opens in a new tab)). For example: blockchain indexers, payment processors, SDK (opens in a new tab), etc.
A more detailed description of this protocol can be found here (opens in a new tab). The set of methods provided by the API is described here (opens in a new tab).
Advantages of this service over deploying your own node
- It eliminates the need for complex maintenance and updates of the node (especially demanding and costly in the case of an archival node)
- It reduces the risk of out of sync error
- It provides access to historical data
- It offers high availability
Connecting to the Liteserver
To connect to the Liteserver, you need to use an application or libraries with a Liteclient function.
You need to specify the Server and Public key or download the global.config.json file with the ready-made configuration for connection.
You can obtain this data in Tonconsole (opens in a new tab) after selecting a plan.
Access to two instances of Liteservers (Server #1 and Server #2) is provided,
and it is better to specify both for higher fault tolerance (if your software supports it).
Rate limits
Each plan has its rate limits, which operate on a sliding window algorithm. The window size is 10 seconds. Therefore, with a rate limit of 1 RPS, the maximum number of requests is 10 requests per 10-second period.
The maximum RPS for current plans is 50. Check with the t.me/tonrostislav (opens in a new tab)([email protected]) for the custom plan.
To obtain rate limit data, the service provides an API method:
TL scheme for liteapi method:
liteProxy.requestRateLimit#14cb3f0c limit:int per_time:int = liteProxy.RequestRateLimit;
---functions---
liteProxy.getRequestRateLimit#f0f83e86 = liteProxy.RequestRateLimit;Where: rate limit = limit / per_time[s]
Archive node access
By default, the service provides access to an archival node for obtaining historical data (i.e., data from the first blocks of the blockchain).