A USDT blacklist execution on Tron, recorded with a null magnitude

The token contract for this asset on Tron recorded a blacklist addition against one target at the execution timestamp above, in block 86,060,882. The transaction that carried it is named in the verification block below, and it is the only execution this record covers.

The action is an in-place freeze: the balance is immobilised where it sits rather than destroyed, and the contract’s total supply is unchanged by it. The freeze kind is one of the facts the digest binds, so it is stated here rather than left to be inferred.

The target is not published. This is a record of an action, not a directory of parties; the transaction reference is what a reader needs to check the record, and it is enough.

The interval, the amount and the digest below were recomputed against two independently operated public Tron nodes, both named in the sources. Agreement on one node is a result; agreement on two is a measurement.

What is measurable here, and what is not

The amount immobilised is 9,705,239.643337 USDT. It was not read at the execution block, because on this chain it cannot be: a call against contract state at a past block is refused outright rather than answered approximately. It was rebuilt instead from the contract’s own transfer log, which a standard node does serve for past blocks. Take the balance the node reports at its current head, pin that block, and undo every transfer naming the target between the execution block and it; what remains is the balance at the end of block 86,060,882. Running the same arithmetic in the other direction — from zero at the contract’s first block, forward — reads a different stretch of the same log and must produce the same figure. The two nodes were each read separately, 42 log queries apiece, and returned the same units.

Magnitude is null. Magnitude v1.0 is the immobilised amount as a share of the asset’s own supply on the same chain, and both halves have to be read at the execution block for the ratio to be deterministic. Recovering the amount from the transfer log does not recover the denominator: total supply moves for reasons a single target’s transfer history does not record. A share without its denominator is not a share, so the entry carries null with the reason. The same rule forbids dressing an unreadable measurement as a whole-supply freeze.

The initiation endpoint is 2026-09-08T07:59:33Z, and the interval is 69s. That endpoint is not an observation of ours. It is the timestamp of the block carrying the precursor transaction named in the verification block below, block 86,060,859, and any node that serves this chain’s history will hand it over: fetch that transaction, see which block it is in, read that block’s timestamp. The interval is the same subtraction anyone can do — the execution timestamp above, itself the timestamp of the block carrying the execution transaction, minus this one. The timing table states it in whole minutes, as the entry format does; the two timestamps it sits between give it to the second. One interval is one reading of one execution. It is not a rate, it is not offered as typical, and an issuer can change how it executes and take it to zero without telling anyone, ourselves included.

An amount beside a null magnitude is not a defect in the entry. It is what this chain looks like through definitions that refuse to guess: what can be recomputed is published with the arithmetic that produces it, and what cannot is recorded as a blind spot and never as a zero.

The same day, and what was reported about it

From the same contract’s public event log, 2026-09-08 carried 59 blacklist additions in total. The one recorded here is the first of them.

Public reporting of that day attributes a subset of those additions to a single operator and puts the subset at about 39,273,713 USDT across ten addresses. That figure and that attribution are reproduced here as an external claim, with the source below and the date it was retrieved; they are not a finding of ours. Which transactions belong to the reported subset is an off-chain judgement and is not readable from chain state, so this entry neither adopts the grouping nor reproduces the per-address figures that rest on it. It records one execution, and the only claim it makes is the one the digest covers.

The Bulletin takes no position on whether this or any other freeze was warranted. It records that one happened, when, and how to check that it did.