> For the complete documentation index, see [llms.txt](https://coinsdo.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coinsdo.gitbook.io/docs/coinget/how-to/how-to-add-a-ton-receiving-record.md).
# How to add a TON receiving record
**On-chain Address Formats**\
TON addresses exist in multiple encoding formats (such as EQ and UQ). These are different representations that point to the same underlying address, which is a standard mechanism of the TON blockchain. CoinsDo displays TON addresses in the EQ format and is fully compatible with both EQ and UQ formats when adding receiving records.\
\
**On-chain Transaction Hash**\
A single TON transaction is executed in multiple steps on-chain, resulting in the generation of several different hashes. While different platforms may display different hashes, they all correspond to the same on-chain operation. The CoinsDo system specifically identifies and utilizes the B hash from the transaction sequence.\
\
**CoinsDo Add Receiving Record**\
When filling in the "Transaction hash" field, please ensure you use the B "Tx hash" from the transaction sequence. For the receiving address, you may use either the EQ or UQ format address (as shown in the reference image below).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://coinsdo.gitbook.io/docs/coinget/how-to/how-to-add-a-ton-receiving-record.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.