What these tools do
Four small utilities for the questions that come up every day when you build on TON and that are annoying to answer by hand: which form of an address to give someone, how many nanoton a balance is, which of the three hashes of a message an explorer is showing, and what a liteserver meant by 403 or 651.
Each tool does one job and links to the chapter of the documentation that goes deeper. None of them needs an account, a key or a plan.
Everything runs in your browser
The converters and the hash tool load a copy of @ton/core, the reference TypeScript library of TON, and do the work locally. An address, a BoC or an amount you paste is never sent to a server — not to TONNode and not to anyone else. You can open a tool, disconnect from the network and keep using it.
That also means the tools cannot answer questions that need the chain: whether an account is deployed, what a jetton's decimals are, whether a message was included. For those you need a node — a private liteserver with your own key, or the mempool stream for messages that have not been included yet.
Where the numbers come from
The error reference restates the error chapter of the LiteServers documentation for the TONNode gateway, and cites the file and function in ton-blockchain/ton for every code the node software itself produces. The message-hash tool computes the three fields the TONNode mempool stream carries for every pending message — cell_hash, norm_hash and sha256 — and its implementation is tested against 72 real mainnet messages taken from the stream's own fixtures. The unit converter is plain integer arithmetic: 1 GRAM is 10⁹ nanoton, and a jetton's raw unit is 10^decimals of its display unit.