Acc. IV · Rollupia magica — rollup-as-a-service cultivar, cultivated 2024
Wizard — Rollup-as-a-Service
Product engineer · 2024 – 2026 · AltLayer
AltLayer's customer-facing surface for launching and operating production OP Stack and Arbitrum Orbit rollups from a guided UI.
Rollupia magica — rollup-as-a-service cultivar, cultivated 2024
Field notes
The context
Launching a production rollup normally means hand-rolling infrastructure. Wizard turns it into a guided UI — which puts the complexity on the frontend: two rollup stacks with different launch semantics, live deployment state, fee flows, fraud proofs, and the billing and admin tooling that backs paying customers.
Cultivation
What I built
- Shipped the OP Stack launch workflow — fund dialog, deploying-status surface, and the fraud-proof UI built on Dispute Games and the Challenger pages.
- Built the Arbitrum Orbit launch flows — Playground and Mainnet deployment with add/edit form parity, mainnet order-form adjustments for the production tier, and a terminate flow for live deployments.
- Built the RaaS deployments dashboard — overview metrics, side navigation, deployment cards, per-rollup details page layout, and the submitted-forms / orbit-list view.
- Shipped the rollup detail surface — Bridge and Data Availability sections, external Blockscout proxy with /stats-service prefix routing, and the public rollup-info sharing flow.
- Implemented fee withdrawal for OP-Stack mainnet rollups.
- Built RaaS Billing & Admin — costs list with full CRUD (MSW-backed in dev), withdraw-fee percentage per client, service-fee balance and payment tracker in agreements, the Stripe payments/subscriptions migration, a manage-clients UX overhaul, and multi-link agreement support.
- Refactored frontend code and introduced domain-driven design architecture as the product evolved into multiple variations merged under shared implementation patterns — supporting convergence across RaaS, AVS-as-a-Service, and Autonome.
- Translated Figma wireframes into production-ready, responsive implementations with the design team, and kept the surface stable through frequent change with a shared multi-step FormContext, theme-driven primitives, and Playwright data-testid coverage across client and payment paths.
Root system
How it works
One unified React frontend powers the whole Wizard product family (RaaS, AVS, Autonome, Bot, Admin). Launch flows share a multi-step FormContext with persisted state; TanStack Query and Zustand split server and client state; wagmi/viem/RainbowKit handle the onchain edges (funding, fee withdrawal, dispute games); MSW backs admin CRUD in development; Playwright covers the critical client and payment paths.
Harvest
Outcomes
- Both rollup stacks shipped end-to-end — OP Stack with dispute-game fraud proofs, Arbitrum Orbit playground and mainnet — live at wizard.altlayer.io.
- Billing and admin tooling operating against real production rollup customers, including the Stripe payments migration.
- Domain-driven refactoring held the surface maintainable as RaaS, AVS, and Autonome converged into one frontend.
Infrastructure UIs are state-machine problems. Modelling launch flows as shared, resumable multi-step state — rather than per-product forms — is what let three product lines converge into one frontend without a rewrite.