財務

Check TRON USDT Blacklist in Telegram

Reply to a Telegram message with the current TRON USDT contract blacklist status for an address.

Setup

Connect the same Telegram bot to Receive a Telegram message and Reply in Telegram. In n8n, connect the bot to Telegram Trigger and Telegram Send Message. Activate one format. A bot can have only one active webhook subscription and must have access to the chat. Public group messages can expose submitted addresses to group members.

Behavior

Send a TRON Base58Check address as the complete message. The workflow validates its checksum through a TRON mainnet node and reads the USDT contract’s getBlackListStatus(address) view. It replies to the original message in the same chat with the returned status. An invalid address receives a format message; an unavailable or malformed node response fails without claiming a status. This is a point-in-time contract reading, not a general fraud or sanctions check. Recheck before acting: status and node data can change.

The public TronGrid endpoint applies rate limits and may require an API key depending on traffic. If needed, configure the TRON-PRO-API-KEY header as a secret on both HTTP nodes in the chosen format. Requests disclose the address to the node service. Each valid request makes two API calls. A failed or uncertain Telegram reply may already have been delivered; inspect the chat before retrying.

Inspiration & credits

Changes to the source

Query the current USDT contract state instead of treating TronScan’s historical blacklist transactions across stablecoins as current USDT status. Reject malformed responses instead of reporting them as clear.
Validate the complete address and checksum, and reply in the source chat so replies also work in groups.

Adapted from TRON USDT Blacklist Checker in Zie619/n8n-workflows. The matching n8n listing credits FORK SOFTWARE TECHNOLOGIES INC. The original template does not state a separate license.

The collection’s MIT notice is pinned at a later revision. This is the collection notice at that revision; it does not establish a separate original template author’s license. Our changes are listed above; see repository licensing.

MIT License

Copyright (c) 2025 Zie619

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.