LiteServers

FAQ

After purchase, you get 2 servers in the form of: IP address, Port, IP address int format, base64 public key (do not share), hex public key (do not share) And also a link to global.config.json which is the same as mainnet global config, but uses only your private liteservers. You can download the config and save it so you don't have to make requests every time. The config available at the link will NOT change. But don't forget to renew your servers.

We generate a separate private key for each user, which is only available to you.

On our side, we use a C++ load balancer on 9 lite servers, between which we distribute the load.

If you need a dedicated solution: contact us

On our side, we use a C++ load balancer on 9 lite servers, between which we distribute the load.

In addition, we provide 2 balancer servers so we can update them. We recommend using both servers and in case 1 is not responding - send requests to the second one.

Downtime is possible only in case of server updates, and it is minimal.

Also, you can see the status and subscribe for updates on our status server: https://tech.dton.io/status/

As well as on the site developed NOT by us: https://tonstat.us/

We distribute all messages from all tariffs to ALL our nodes around the world, as well as to third-party services and directly to network validators.

In case of high load, messages from more expensive tariffs are prioritised.

We recommend using waitMasterchainSeqno which allows you to execute an arbitrary function when publishing a block. For example, you can get the state of the desired account, or get the block as soon as at least one of our servers around the world gets a new block online.

Each function in the function liteserver list adds 1 request. The counter is reset every second.

No, but at high load times we prioritize more expensive rates with additional messaging.

If the liteservers works, most likely the error is on your side. Check open ports, try to change network provider or run the code on another server or locally.

If this doesn't help - write us in the support chat