Skip to content
Carlo Miguel Dy
← Back to the specimen catalogue

Acc. V · Avs eigenlayeri — restaking cultivar, cultivated 2025

AVS-as-a-Service — no-code EigenLayer AVS deployment

Product engineer · 2024 – 2026 · AltLayer

Deploy a production AVS (registry stack + ECDSA or BLS service manager) from a guided UI instead of hand-rolling EigenLayer plumbing — described in the official docs as the world's first AVS-as-a-Service platform.

Avs eigenlayeri — restaking cultivar, cultivated 2025

Field notes

The context

Teams building in the EigenLayer ecosystem needed to deploy and operate AVSs — operators, restaking strategies, metadata — without hand-rolling the contract plumbing. The AVS surface had to live inside the same unified Wizard frontend as RaaS and Autonome without duplicating platform code.

Cultivation

What I built

  • Owned the Deploy AVS multi-step flow and the state-persistence model behind it, keeping the wizard resumable across steps and aligned with the rest of the Wizard frontend's state architecture.
  • Built the AVS app store / marketplace UI — the listing experience plus environment-aware gating that controls what surfaces to customers in production.
  • Implemented AVS name validation in the deploy flow and the team-settings promote / kick actions on top of the shared org / auth model.
  • Contributed to the shared design system and platform plumbing used across the Wizard product family, so AVS-only changes inherited shell-wide improvements without duplication.
  • Extended Playwright end-to-end coverage on the shared flows the AVS surface depends on.

Root system

How it works

One product domain inside the unified Wizard frontend. The deploy wizard persists step state so a team can resume mid-configuration; environment-aware gating decides which marketplace listings surface in production; org, auth, and design-system primitives are shared with RaaS and Autonome rather than forked.

Harvest

Outcomes

  • Deploy AVS flow, marketplace, and team management live at wizard.altlayer.io/avs.
  • AVS surface inherits shell-wide platform improvements with zero duplication — one frontend across RaaS, AVS, Autonome, Bot, and Admin.
Pressed leaf — what it taught
A product surface inside a platform frontend should own its domain logic and nothing else. Investing in the shared org/auth/design-system layer paid back every time a new product domain landed.