DNS/CDN/frontend hash drift
EigenLayer's assessment for RD-F-105 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Signal applicable: primary frontend is app.eigenlayer.xyz (now redirecting to app.eigencloud.xyz). The domain migration from eigenlayer.xyz to eigencloud.xyz is announced and allowlist-eligible. However: (1) the domain migration creates new monitoring surface requiring a fresh hash baseline for eigencloud.xyz assets; (2) old eigenlayer.xyz domains must be monitored for potential takeover; (3) EigenLayer's X account was hacked (Unchained Crypto report), confirming active brand-impersonation threat. Score yellow because the domain migration creates a monitoring gap — production hash monitoring must be recalibrated for eigencloud.xyz.
Sources #
- DocsEigenCloud Blog — EigenLayer tagEigenCloud blog confirming domain migration and branding change from EigenLayer to EigenCloudretrieved 2026-04-28
- EigenLayer X Account Hacked — Unchained CryptoUnchained Crypto: EigenLayer's X Account Hacked in Latest Social Media Crypto Takeover — confirms active brand-impersonation threat vector against EigenLayerretrieved 2026-04-28
- EigenLayer protocol profile §9Profile §9: Primary docs docs.eigencloud.xyz (formerly docs.eigenlayer.xyz; redirected to eigencloud) — confirmed documented redirect requiring monitoring baseline resetretrieved 2026-04-28
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 →