Litecoin Address

Detects Litecoin addresses in two forms. Native SegWit bech32 addresses use the human-readable part "ltc1" (distinctive, 85-gated). Legacy base58 addresses are P2PKH with version byte 0x30 (leading "L") and P2SH with version byte 0x32 (leading "M"), 26-35 characters (most 34) — a single-letter prefix that is weaker (75-gated). Prefixes/version bytes/lengths verified against the Litecoin address-prefix docs and documented example addresses.

Type: regex
Engine: universal
Confidence: medium
Confidence justification: The "ltc1" bech32 form is a distinctive fixed HRP (85 when domain-gated). The legacy L/M base58 form is a single-letter prefix that collides with other base58 addresses and has no regex-expressible checksum (75). Neither tier is exported bare — precision comes from (distinctive prefix/HRP) times the mandatory cryptocurrency/wallet domain-context gate plus the noise exclusion.
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

\b[LM][1-9A-HJ-NP-Za-km-z]{25,34}\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

LZyv3r9Tt6o7yUENc9AZf5FbQVe9GxL7w3 — Legacy P2PKH address (L prefix, version 0x30), documented example (34 chars)
MQMcJhpWHYVeQArcZR3sBgyPZxxRtnH441 — P2SH address (M prefix, version 0x32), documented example (34 chars)
ltc1qg82u5u4mhn6n9l5xup0yfl52q3c4z9hsgwlj5n — Native SegWit bech32 address (ltc1 HRP), documented example (43 chars)

Should not match

3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy — Bitcoin legacy P2SH "3" address — intentionally excluded (wrong prefix, collides with Bitcoin)
bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4 — Bitcoin bech32 address — wrong HRP (bc1, not ltc1)
LZyv3r9Tt6o — Too short (below the base58 body minimum)
LZyv3r9Tt6o7yUENc9AZf5-FbQVe9GxL7w3 — Hyphen breaks the run so no contiguous body exists — rejected
litecoin wallet address example placeholder — Template/placeholder context should be excluded even when domain anchor words are present

Known false positives

The legacy L/M base58 form shares the base58 alphabet and 34-char envelope with Bitcoin/Dogecoin addresses and arbitrary base58 tokens; the Base58Check checksum cannot be validated in a Purview-safe regex. The "ltc1" bech32 form is far more distinctive but still lacks a regex-expressible checksum. Mitigation: Both tiers are AND-gated by cryptocurrency/wallet domain context (crypto-wallet-context) within the proximity window plus a template/sample noise NOT-group. The distinctive ltc1 form is 85, the weaker legacy form 75.

References

Collections

Cryptocurrency Wallet Addresses