Liteserver (TON)
Last updated:
Applies to: TON
In more detail
Applications and HTTP or JSON-RPC front ends read TON through liteservers rather than by syncing the chain themselves. A regular liteserver does not store the entire block history; how much state and archive data it keeps depends on its configuration, while archive liteservers keep full history. The same historical query can therefore succeed on one liteserver and fail on another.
Reads that name a masterchain seqno are therefore retention-sensitive, while reads of current state are not.