DNS/CDN/frontend hash drift
Liquid Collective (LsETH)'s assessment for RD-F-105 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
T-09 phase-2 signal; tier-A. Primary domains are liquidcollective.io and docs.liquidcollective.io. No DNS change or frontend hash drift detected in data cache or public sources. The February 2024 brand-impersonation event was via Telegram (a social channel clone), not a DNS/frontend compromise -- confirming production domain remained clean through that incident. Baseline hash monitoring requires external monitoring infrastructure not yet in production.
Sources #
- URLLiquid Collective official websiteLiquid Collective official domain liquidcollective.io; documentation at docs.liquidcollective.io; no DNS/frontend compromise event found in public sourcesretrieved 2026-05-17
- Liquid Collective brand impersonation report - X/TwitterFebruary 2024 Telegram scam was brand impersonation via external clone channel, not DNS/frontend compromise; official domain unaffectedretrieved 2026-05-17
Methodology #
Detect whether the hash of production frontend JS changes versus the prior published hash, or a DNS config change is detected.
See the full factor methodology and distribution across all protocols →