TRON Address

Detects TRON (TRX) mainnet addresses: Base58Check encoding of a 21-byte payload (0x41 version byte + 20-byte address hash), always starting with the letter "T" and exactly 34 characters long. The 0x41 prefix byte fixes the leading character as "T" and the length at 34 (58^34 > 66*256^24; 58^33 insufficient). A single leading letter is weak structure, so detection is context-gated. Prefix/length/charset verified against TRON developer docs and the TRON protocol overview.

Type
regex
Engine
universal
Confidence
medium
Confidence justification
Gated 75, not high: a single leading "T" plus a fixed-length base58 run is weak structure with no regex-expressible checksum, so it collides with other "T..."-leading 34-char base58 tokens. Precision comes from the mandatory cryptocurrency/wallet domain-context gate plus the noise exclusion. The fixed 34-char length is a modest additional constraint but not sufficient alone.
Jurisdictions
global
Regulations
FATF Recommendations, AML/CTF Act (Cth)
Frameworks
ISO 27001, ISO 27701, SOC 2
Data categories
financial
Scope
narrow
Platform compatibility
Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible

Pattern

\bT[1-9A-HJ-NP-Za-km-z]{33}\b

Corroborative evidence keywords

identifier, number, ID, transaction, transfer, payment, deposit, withdrawal, debit, credit, data record, database record, record set, data extract, data export, database table, spreadsheet, data registry, registry entry, master data (+14 more)

Proximity: 300 characters

Should match

Should not match

Known false positives

References

Collections