Fireblocks supports TON transaction comments (also known as ״text_message”) in compliance with the official TON standard. A TON Transaction comment is handled as a transaction “memo”/”tag”, and is notified in the webhook as “destinationTag”.
What are TON comments?
In the TON blockchain, the ״text_comment״ field allows you to attach arbitrary data to a transaction. Unlike blockchains such as Stellar, which use a fixed-format memo field, TON is an open protocol where the message body can contain arbitrary data. The standard TON comment format uses the “text_comment” instruction type to forward comments which are leveraged as memo by convention.
How Fireblocks handles comments
When Fireblocks process a TON transaction which does not align with the TON memo convention, the destination tag will not be populated in the transaction. To support cases that do not adhere to the above TON convention, Fireblocks exposes the TON transaction “message_content” data in the “blockchainInfo” field. This will allow you to:
- Implement custom parsing logic for non-standard formats if needed
- Ensure critical deposit identification data is correctly processed
- Verify our decoding of the comment data
If you are processing deposits or withdrawals that rely on comment data, you should validate against the raw data when necessary.
Recommended action
If your integration depends on TON comments for transaction identification (for example, customer deposits), we recommend:
- Always validating critical data against the raw comment value
- Testing your parsing logic with both standard and non-standard message formats