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
TNPeeaaFB7K9cmo4uQpcU32zGK8G1NYqeL— Address from the TRON developer docs Accounts page (34 chars)TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t— USDT-TRC20 contract address (widely documented, 34 chars)TJCnKsPa7y5okkXvQAidZBzqx3QyQ6sxMW— Address from the TRON protocol overview section 6.2 worked example (34 chars)
Should not match
1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa— Bitcoin legacy address — wrong prefix (starts 1, not T)TNPeeaaFB7K9cmo4uQpcU32zGK8G1NYqe— Too short (T + 32 = 33 chars, below the fixed 34)TNPeeaaFB7K9cmo4uQpcU32zGK8G1NYqeLXY— Too long (T + 35 = 36 chars, above the fixed 34)TNPeeaaFB7K9cmo4-uQpcU32zGK8G1NYqeL— Hyphen breaks the run so no contiguous 34-char body exists — rejectedtron wallet address example placeholder— Template/placeholder context should be excluded even when domain anchor words are present
Known false positives
- A single leading "T" plus a 34-char base58 run collides with other "T..."-leading base58 tokens; the Base58Check checksum cannot be validated in a Purview-safe regex. Mitigation: The tier is AND-gated by cryptocurrency/wallet domain context (crypto-wallet-context) within the proximity window plus a template/sample noise NOT-group; held at 75.
References
- Accounts — TRON Developer Hub (Base58Check "T" prefix, length 34, 0x41 version byte)
- TRON overview — mainnet addresses begin with 41 (base58 worked example)