User guide

Getting started

1. Sign in through Telegram and open My account.
2. Enter TRON addresses, or submit a CSV list under Payment checks.
3. Review the price before confirming. Address checks are confirmed here; payment batches are confirmed in Telegram.
4. Read results here. Use Telegram for top-ups, watches, notifications and batch management.

Account & sign-in

Sign in through Telegram’s official authorization page. The website and bot share your account, balance and trial. You will return here after authorization.

This website does not receive Telegram login codes or passwords. On first use, allow the corresponding bot to send you messages so it can deliver query notifications.

Both languages and bots use the same Telegram user ID. They share balance and trial access; switching languages or signing in again does not grant a new trial. Reports and activity are private to the signed-in account.

The website does not generate a six-digit sign-in code. If an old tab still shows the retired code page, close it and open the current sign-in entry. Complete Telegram’s own verification only on its official page.

Pricing & refunds

Same as Telegram: 0.50 USDT per address per check. Valid trial checks apply first to the bound address. Trials cannot be renewed; failed checks are refunded.

Valid trial checks apply first, so the actual charge may be lower. Addresses without enough balance are skipped; failed checks are refunded. Review these addresses before confirming. Only this button starts charging.

Preparing lists, previewing prices and browsing public proposal or event lists are free. Reloading a saved report does not query again or charge. New checks and retries of incomplete items review eligibility again; refreshing completed items never charges twice.

Items without sufficient balance are skipped without charge. Failed lookups and unavailable solidified receipts refund the paid balance or trial use. Refunds do not extend the trial. Balance is displayed as the USDT equivalent of prepaid service credits.

Trial access

One trial per Telegram ID, valid for 3 days from first registration. It covers 1 fixed address, 1 trial watch slot and up to 5 checks. The address binds on first use and cannot be changed.

An address cannot claim trials across multiple accounts. After expiry there are no free watch slots and unused trial checks expire; paid slots are unaffected. Trial checks cannot purchase permanent slots.

Address checks

Up to 20 addresses per request. Top up and manage watch slots in the bot; both use the same account.

Enter one address per line in Overview. Review price prepares a confirmation page without charging. It shows the address list and maximum cost; valid trial checks can reduce the actual charge.

The saved result contains the risk level, USDT balance, proposals and available chain evidence from that check. Start a new check for the current state.

Payment batches

Supports official USDT on TRON mainnet only. Choose recipient risk screening or payment verification, then upload or paste a UTF-8 CSV with up to 500 rows and 256 KB.

Keep split payments on one business row. An event referenced by multiple business IDs is not counted twice; confirm the business mapping manually. Preview the batch, then review and confirm costs in Telegram. Your confirmation link expires after 24 hours. Submit checks and view results here; manage notes, retries, exports and exceptions in Telegram.

Reading results

Payment verification covers supplied transaction hashes only and cannot find omitted payments. A matching amount means the matched transfers in those transactions agree with the plan; it does not prove business purpose, wallet ownership or accounting recognition.

An unavailable result does not mean risk-free or unpaid. Network errors, unavailable solidified receipts and conflicting event mappings are marked separately. Do not treat unknown states as success or failure.

Risk checks are snapshots, not safety guarantees. Pending proposals can be cancelled or executed. Open full query data and transaction evidence to inspect the available records. A query does not enable ongoing monitoring automatically.

Watches & notifications

Use the corresponding language bot to top up, buy watch slots, add addresses and change notifications. Overview shows active addresses and available slots. Free monitoring ends when the trial expires. A retained address record does not mean monitoring is still active.

Allow the corresponding bot to send messages at first sign-in, or open the bot and start a private chat. Telegram provides batch completion notices and detailed operations. Notifications are not guaranteed to arrive before chain execution.

History & records

These checks include website, Telegram and payment batches. Telegram check history shows addresses, times, prices and refund status. Open saved website reports below.

Saved results from this query. Refreshing neither updates the data nor charges again. Start a new query for the current state. Only this Telegram account can read this report.

Overview shows the latest 5 website reports. Query history lists up to 30 saved reports and 30 checks across channels. Balance activity shows the latest 30 top-ups, charges and refunds. Payment checks lists the latest 30 batches. Older Telegram checks show existing receipts; report content that was never saved is not reconstructed.

Public ledger and methodology

Events, proposals, address aggregates and batches are public chain history, not a current address-risk report. Address checks require sign-in and price confirmation.

Proposals pair with executions by multisig transaction ID. Recent unexecuted proposals are pending; those older than 7 days are listed separately as long unexecuted. State-event matching uses address and timing and is inferred, not a direct chain link.

A submission gap over ten minutes starts a new batch. Temporal grouping does not prove common ownership or a common report.

Intervals, percentiles and reaction coverage use executed paired samples only and do not guarantee future warning time. Same-block executions have no reaction window. Release-time distributions include released addresses only and cannot predict whether another address will be released.

Counts follow the range filter; all-time metrics retain their full-history scope. Hours and weekdays use UTC. Contract function names, transaction hashes, API fields and enums retain their protocol spelling.

Latest event means the newest chain event; last checked means the collector's most recent check. Quiet event streams do not mean collection stopped. Current signers and threshold are read from the contract and may be cached; failed reads show unavailable rather than reconstructing an incomplete set.

General ledger API, Atom and CSV feeds are public and rate/row limited. Address-specific queries and filtered exports still require sign-in and price confirmation.

Telegram commands and language

The English bot uses English for replies, buttons and notifications; the Chinese bot uses Chinese. Client settings and legacy account preferences do not change the current bot's language. Use /lang to open the other bot; balance, trial and watches are shared. Language-switch links retain the destination language name. Brands, commands, addresses and hashes retain their original spelling.

Typing the bot username and an address in another chat provides a private-check entry. Risk checks run privately under the shared account entitlement; inline entry does not bypass pricing. New checks and refreshes of current state consume an eligible trial use or balance. Reading saved web reports does not query or charge again. Completion notifications use the bot associated with the operation; watch and top-up notices use the most recently used bot without duplicate delivery.

Text in old chat messages is not rewritten automatically. Use /help, /start or open a new result to see the current version. Legacy language buttons still provide a working route.

Payment tools

Check before payment. Resolve exceptions after payment.

Payment list change check

Upload approved and planned payment CSVs using the payment template. Business IDs identify additions, removals and changes to recipients, amounts or senders. Repeated recipient/amount combinations across IDs are review candidates, not proof of duplicate payment. Preparation is free. After confirmation, recipient risks are checked for planned entries and removed original entries, billed by unique address. An old recipient replaced in the planned file is not the destination checked in that planned entry.

This compares file fields, not encoded wallet transactions. It does not sign or broadcast. File agreement does not replace checking the transaction in your wallet.

Transaction diagnostics

Provide a payment CSV with transaction hashes, recipients and planned amounts. Solidified TRON mainnet official USDT receipts supply execution results, matching transfer events and recorded energy/bandwidth fees. Fees are receipt values, not estimates. Missing solidified receipts do not prove failure or lost funds; those units are refunded. There is no execution trace or visibility into platform/merchant internal processing.

Bookkeeping difference review

Upload payments and a bookkeeping export, then select inclusive start/end dates and the accounting timezone. Timestamps without an offset use that timezone. Maximum period: 366 days; UTC and UTC+8 are supported.

Bookkeeping headers: entry_id,business_id,address,amount,booked_at,txid. The first five are required; txid is optional. Use positive amounts up to six decimals and full timestamps, for example 2026-10-17T12:00:00+08:00. Business mapping is customer-declared; equal amounts alone do not establish purpose.

Identical rows sharing an entry ID count once; conflicting versions require review. Chain payment time and bookkeeping time are checked separately. Missing chain timestamps prevent period agreement; conflicting entry IDs have no automatic amount total. Missing-in-scope, cross-period, mapping differences, amount differences and incomplete chain evidence remain separate states. Bookkeeping rows without a supplied payment ID are listed separately. Agreement across imported records does not certify financial recognition or source completeness.

Pricing, saved results and operations

Diagnostics and bookkeeping use the existing price and trial rules per unique transaction-hash/recipient pair. Missing-hash items cannot run and are not billed. An executed-failure receipt remains a valid lookup; unavailable receipts or failed services are refunded. Review the price in Telegram before confirming.

The website previews inputs, requests queries and reads saved reports. Use /payments to confirm, /payment_note for notes, /payments_retry for a new check, and /payments_export for CSV. Retries require another cost confirmation and retain the earlier report, notes and source digests. Each file supports up to 500 rows and 256 KB. Inputs are not sent to third-party models. Reports preserve source SHA-256, rule version, period and event evidence; CSV contains comparisons and source digests. Reports are private. These tools do not connect to or write your general ledger or execute payments.