Reading 9 event streams, every 10s
Almost nobody is listening. Utrust Lab builds the tools that are — small, verifiable instruments that turn a public on-chain event into a warning that reaches a person in time to matter.
Collected by us, from the chain, into our own ledger. Not licensed, not resold, not estimated.
How we work
Every tool we build is the same shape. What changes is which chain we point it at.
We keep our own event ledger rather than querying somebody else's API at request time. It costs more and it is the only way a number on our page can be traced to a block.
The ledger is append-only and every row keeps the raw event beside the parsed one, so a parsing bug we fix next year can be replayed over everything we already hold. When the collector dies it resumes from the last cursor it wrote to disk: a crash costs us minutes, never a gap.
9 event streams polled every 10s 17,850 events held
A verdict is computed by a single module and every surface renders it. The bot and the site cannot disagree about an address, because neither of them is allowed to form an opinion.
That module returns a card, not a sentence: the level, the evidence behind it, and what a reader is entitled to conclude from it. Wording lives in the templates and can change freely; the judgment cannot change without changing the one file every surface reads.
1 module 3 call sites 0 second opinions
A page you have to remember to open is not a warning. The moment something lands on an address you watch, a message goes out — measured in seconds, and the delivery is written down before it is sent.
Delivery runs in a different loop from collection, so a slow page of chain history can never hold up somebody's alert. And because the intent is written down before the send, a process that dies mid-flight resends on restart instead of quietly dropping the one message that mattered.
target under 30s written down before sending
We never ask for a private key, a seed phrase, or a token approval — not in any product, not for any reason. Nothing we build has a code path that could move your money, which is why nobody can be tricked into authorising one.
We store the Telegram ID, monitored addresses, credit ledger, sign-in sessions and query reports required to provide the service. No IP addresses, user agents or chat contents. The website uses essential sign-in cookies.
no key requests no approvals no transfer code path
One product, running in public. We would rather show you a live ledger than a roadmap.
USDT freeze-risk alerts on TRON. UAlert tracks freeze proposals; the bot monitors addresses and sends alerts. Sign in on the website through Telegram to query address risk using the same trial and paid balance.
These are not values on a wall. Each one is a test that fails the build if it stops being true.
Statistics are re-derived from the ledger on each page load — never typed into the copy. A test scans all our text for hard-coded figures and rejects them, because a number that drifts from its source is worse than no number.
If a lookup fails, the page says the lookup failed — it does not show a zero. If a freeze happened before our records begin, we say we can't date it rather than pointing at the nearest event we happen to have.
No IP addresses, user agents or chat contents. The website uses essential secure sign-in cookies and stores account ownership and billed reports to prevent duplicate charges and support refunds.
We tell you what the chain did. We do not predict what it will do, we do not offer to reverse it, and we do not sell hope to people who have just lost money. A test rejects any copy that promises an unfreeze.