TON
Everything on this page is generated from the running deployment. If a capability stops being served, the row for it changes rather than staying true-looking.
| What | Method | On TON | Notes |
|---|---|---|---|
| Read a balance | balance.get | Not here | Not commercially available on this network. |
| Read network state | network.status | Not here | Not commercially available on this network. |
| Watch for a payment | payments/watch | Available | Followed by the light acquisition path, one bounded read per pass. |
TON is NATIVE, chain id F6OpKZKqvqeFp6CQmFomXNMfMj2EnaUSOXN+Mh+wVWk=.
Its engine here is ton.
What TON means by settled
Reported in this chain’s own vocabulary. It is never translated into a shared “confirmed”, because the translation is where the money goes missing.
This chain has a protocol condition for finality: a block either meets it or does not, and waiting longer does not make a block that has met it any more final. Depth is not meaningful here.
- The strongest thing TON says is
MASTERCHAIN_COMMITTED. - Its intermediate condition is
SHARD_COMMITTED. - Depth is not what settles a block here, so this deployment does not count to one.
Paying on TON
This deployment follows TON for payments and can watch one destination for one asset.
- The asset this deployment can identify here is TON (Toncoin), named as the native coin, with 9 decimals read from the contract rather than assumed.
- Amounts are compared as an integer count of the smallest unit. A float would round, and a rounded payment is a dispute.
- Detection and settlement are separate standings. You choose which one your checkout ships on.
A destination on TON needs a comment. carried in the message body. A watch without one is refused when you open it, rather than accepted and never matched.
Known limitations on TON
- Free Beta: nothing is priced and no availability is promised.
- Answers here are what a source said, with nothing corroborating them. That is often fine and it is never hidden.
- Source independence is unestablished here: this deployment cannot show that two sources it might ask are operated separately, so agreement between them is treated as availability rather than as evidence.
- No commercial read method is available on TON.
- No transaction history, no archive and no broadcast on the Beta surface.