DNS/CDN/frontend hash drift
Liquity V1 + V2 (LUSD / BOLD)'s assessment for RD-F-105 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
DNS/frontend hash drift signal (T-09 phase-2 signal tier, tier-A). Applicable: yes — liquity.org serves the primary interface. Threshold: hash change in DNS A/CNAME, TLS cert, or JS bundle vs baseline without change-management allowlist match. Current posture: no DNS change alerts, no TLS cert rotation alerts, no frontend compromise reports for Liquity identified. No historical frontend attack on Liquity documented. Static assessment cannot definitively confirm production hash baseline without live monitoring pipeline. Green posture on available evidence.
Sources #
- URLLiquity official websiteLiquity primary domain liquity.org; no DNS incident or frontend compromise reported in any public sourceretrieved 2026-05-16
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 →