$1.2B+
Reported impersonation loss, trailing twelve months.
OPERATION
How a lookup becomes a record.
One independent query. The RX record opens beside it. Threat hosts stay defanged.
THREAT BRIEF
The information layer is hit first.
Small repositories are cloned first. The drain is a second-order event.
70%
Share of cloned socials appearing in the first week.
<90s
Median drain after the first malicious click.
n+1
Clone burst after a founding tweet. Independents have no brand desk.
STANDARD
How an RX ID is born.
Same series for a three-person GitHub org and a layer-one. There is no community-lite identifier.
IN
First-party ingest
Only surfaces the project controls: site, X, docs, Discord. Third-party directories are not sources.
AU
Authenticate
Channels are bound to a single RX-series ID. Independents receive RX-0xxx — the same format as majors.
WA
Watch
A 24/7 window on impersonation and phishing hosts. Flags land on the record before a transaction exists.
WHO QUERIES
Need for a canonical page, not follower count.
Team size on the horizontal. Need for one authoritative record on the vertical.
SIZE OF TEAM →
REGISTRY
Live-feeling index. Filters are real.
Majors sit beside independents. Independent hides layer-ones and large L2s.
| Project | Type | Status |
|---|
INDEPENDENT LANE
The Telegram-group protocol gets the same record as the L1.
Same RX format as the L1. No brand-protection team required. Query the independent set below.
Q4 2026
The registry opens with the watch window already running.
No token. Public waitlist on X. Application remains dark until launch.