Ethereum restaking analytics platform — designed end-to-end, from information architecture to component flows
Executive Summary
Restaking.Info is a comprehensive EigenLayer analytics platform covering the full restaking stack — TVL overview, AVS status and metrics, operator tracking, LST and LRT distribution, permissionless tokens, rewards, and on-chain events — all in a single, readable interface with nine distinct views and per-entity detail pages.
The product targets a technically sophisticated but time-poor audience: crypto-native users who need confidence in their positions without having to parse raw contract data or cross-reference three different tools. Each section has its own depth — from a global EigenLayer overview down to individual AVS bios like EigenDA, a data availability solution with 10 MiB/s of write throughput.
Platform structure
Business model
All restaking data — TVL, operator metrics, AVS status, LST distribution — exposed through a paid API. Protocols, dashboards, and developers pay for programmatic access to clean, normalised on-chain data without having to index it themselves.
Operators — starting with Nethermind's own — can pay to be featured and promoted within the dashboard. The platform turns its own analytics into a distribution channel for the operator business, creating a direct commercial loop between the product and Nethermind's restaking infrastructure.
A $1.99/month subscription that removes promotions from the interface — a lightweight way to monetise power users who want a clean, ad-free experience while keeping the core product free.
How it works
Link any EVM wallet. The dashboard instantly reads all restaking positions across supported protocols — no manual input required.
Total restaked value, rewards accrued, operator health scores, and slashing risk — all in one view, updated in real time.
Restake, withdraw, or switch operators directly from the dashboard. Smart alerts surface critical changes before they become costly.
Design principles
Surface the 20% of data that drives 80% of decisions. Hide the rest behind progressive disclosure.
Every number is attributable. Users can always drill down to the on-chain source.
EigenLayer, Symbiotic, Karak — the DS is built to extend to any new protocol without a redesign.
Analytics without action is noise. Every insight leads to a clear next step the user can take.
Problem & Success
The Challenge
The restaking ecosystem exploded in complexity faster than tooling could keep up. Users manage positions across multiple protocols, operators, and AVSs — but no single interface unified this data. The result: time wasted, mistakes made, and opportunities missed.
User voice
User or stakeholder quote will go here — a data point or verbatim feedback that anchors the problem.
The Goal
Success was defined across three key dimensions, each tied to measurable outcomes.
Strategy & Insights
Key Insight
[Placeholder — the single research finding that redirected the design. E.g. "Users weren't confused by the complexity of restaking — they were confused by the inconsistency in how different protocols named the same concepts. A unified terminology layer was more valuable than any new feature."]
Information Architecture
The IA was organised around the user's mental model — not the protocol's technical structure. Portfolio → Positions → Operators → Rewards, not the other way around.
Competitive Benchmarks
Benchmarked against leading DeFi analytics and on-chain data platforms to identify established patterns in data-dense dashboards and gaps specific to the restaking space.
Iterations
The first version looked like every other crypto dashboard. The pivot was about restraint — removing data until only decisions remained.
Early wireframes mapped out all sections of the platform — global overview, AVS detail pages, LST/LRT distribution, permissionless tokens, and the support plan. The lo-fi prioritised information architecture and data hierarchy over visual treatment.
Overview
Overview v2
AVS detail
AVS early
Permissionless
[Placeholder — specific failure from usability testing. E.g. "100% of testers opened the wrong section first. Organising by protocol instead of by user goal forced users to mentally translate before they could act."]
Designed and owned entirely in Figma — from component architecture to interactive flows. Every major section is a named flow covering the full state space: the AVS detail maps three sub-views (Total Value, Operators, Re-stakers); the Operator flow covers the list, search match, empty state, 404 error, operator detail, and the AVS-Operators tab. Nothing left to chance.
AVS flow
Operator flow
Desktop and Mobile
Design System
A DeFi dashboard is only as trustworthy as it looks. Every component was built to communicate precision — tight spacing, monospaced numbers, semantic colour for risk states.
Inter for UI labels and body. Monospaced numerals throughout — every number right-aligns and scales identically regardless of digit count.
A strict semantic palette: green for healthy, amber for caution, red for risk. No decorative use of colour — every hue carries meaning the user can rely on.
Position card, operator health badge, reward ticker, risk meter, wallet connect flow — a component set covering every interaction pattern in the dashboard.
Each component is protocol-agnostic by design. Adding Symbiotic or Karak support requires no new UI patterns — just new data piped into existing components.
Results & Retrospective
Did we hit the goals set in section 2? Here's where the numbers and the human feedback meet.
User voice
Qualitative user feedback / testing quote will go here.
What I'd do with more time
The dashboard is inherently desktop-first, but critical alerts (slashing risk, reward milestones) need to reach users on mobile. A lightweight iOS/Android companion is the clearest next surface.
Operator health data is rich but hard to parse at a glance. An LLM-generated plain-English risk summary per position — updated daily — would dramatically lower the cognitive load for non-expert users.
Power users often manage restaking across 3–5 wallets. A portfolio aggregation view — treating multiple wallets as one entity — is a high-value feature with clear technical complexity worth solving.