AltLayer Documentation
  • 👋Welcome
    • Overview
  • Restaked Rollups
    • VITAL for Decentralised Verification
      • Tier-1 Finality
      • Tier-2 Finality
      • Tier-3 Finality
    • MACH for Faster Finality
      • Interoperability via MACH
    • SQUAD for Decentralised Sequencing
    • Staking of dApp Token
  • Wizard
    • Introduction
    • Technical overview
    • Create AVS
    • Manage AVS
    • Operator management
    • Hosted operator API (BLS based)
    • Custom AVS specification
      • Constructor specification requirements
      • Import Externally-Deployed AVS
    • Report bug or submit a feature request
  • Autonome
    • Deploy AI Agent
    • Autonome API guide
    • Uploading your own agent framework
    • Twitter/X login troubleshooting guide
  • ♾️AltLayer-Facilitated Actively Validated Services
    • Overview
    • AltLayer MACH AVS
      • Operator Guide
      • User Delegation Guide
    • Cyber MACH AVS for Cyber L2
      • Operator Guide
      • User Delegation Guide
    • DODOchain MACH AVS for DODO Chain
      • Operator Guide
      • User Delegation Guide
    • Fast Finality Layer for Soneium
      • Operator Guide
      • User Delegation Guide
    • Xterio MACH AVS for Xterio Chain
      • Operator Guide
      • User Delegation Guide
  • Upgrade Guide
  • 🥩ALT Restaking
    • Staking Info & Parameters
    • Restake ALT
    • Delegating reALT
    • Check and Claim Staking Rewards
    • Unstake ALT
    • Migration from Xterio (Legacy) ALT Pool to Xterio Restaked ALT Pool
    • Testnet reALT faucet
  • Rollup-as-a-Service
    • What is Rollup-as-a-Service (RaaS)?
    • AltLayer's RaaS Offering
    • RaaS Onboarding Guide
      • Optimism Rollup FAQ
      • Arbitrum Rollup FAQ
    • AltLayer Ecosystem
    • Clients in the Spotlight
    • Pricing Model
  • External Integrations
    • Account Abstraction using Biconomy
    • Enabling permissionless interoperability on AltLayer Rollup with Hyperlane
      • Deplying Hyperlane Warp Routes for ERC20 Token Bridging
      • Running Off-chain Agents
      • Setting up the bridging UI
    • Cross-chain Interoperability using Celer
      • Fungible Token Bridging
      • Non-fungible Token Bridging
      • Generic Message Passing
      • cBridge SDK
  • AltLayer's In-House Rollup Stack in Depth
    • How does AltLayer's in-house rollup stack work?
    • Decentralized Sequencer Set
    • Security via Fraud Proof
  • Rollup Types
    • Flash Layer Rollups
      • Example Use cases
        • NFT Mint Events
        • Games
        • Event Ticketing
    • Persistent Rollups
  • Core Features of AltLayer's In-House Rollup Stack
    • Modular
    • Elastic
    • Multi-VM Support
    • Fraud Proofs
    • Decentralized Sequencers
    • Tiered-Finality
  • FlashLayer Showcase
    • AltLayer's POAP NFTs Collection Mint
      • Performance Test in the Wild
    • Dark Forest Community Round
    • Oh Ottie! NFT Collection Mint
    • Dark Forest Community Round for Jump Crypto's Pit Event
    • Ottie 2048
    • Other demos
      • Fraud Proof Demo
      • Flash Layer Demo
      • Rollup Launchpad Demo
      • FlashGPT Demo
  • Implementation Status
    • Roadmap
    • Development Status
  • Community & Support
    • Community
    • Support
Powered by GitBook
On this page
  • What is AVS?
  • How does Wizard create and manage AVS?
  1. Wizard

Technical overview

PreviousIntroductionNextCreate AVS

Last updated 7 months ago

Wizard is a no-code platform where builders can easily choose, deploy and manage their preferred AVS solutions, including MACH (a fast finality network for rollups), bridges or co-processor - enjoying an experience that is 10x faster and 100x easier than a manual AVS deployment pipeline.

What is AVS?

An Actively Validated Service (in short, AVS), proposed and popularized by EigenLayer, is a network of operators that offer decentralized services such as sequencing and asset bridging to its users. To ensure liveness and safety of an AVS, the network borrows economic security from Ethereum via EigenLayer’s restaking mechanism. Restaking makes it possible for already staked ETH to be reused to service AVSs. Misbehaving operators that violate liveness or safety guarantees get their stake slashed.

How does Wizard create and manage AVS?

Wizards provides an intuitive UI that allows users to create and customize their AVS based on their needs.

After customizing the AVS, users can proceed to AVS deployment, which will include both on-chain and/or off-chain components. This includes selecting which service manager (either a Template or Custom) and strategies to support.

Wizards will deploy the following on-chain components

  1. AVS Base contracts

  2. Service manager contract (either a Template or Custom)

Wizard includes an AVS factory contract that helps you deploy the following base contracts.

  • Registry Coordinator

  • Service Manager Base (ECDSA or BLS)

  • Stake Registry (ECDSA or BLS)

  • Index Registry

  • Operator State Retriever

  • BLS Apk Registry

After the base contracts are deployed, Wizard will deploy the template service manager contract and upgrade the service manager implementation to the newly deployed contract.

For BLS-based service manager template, AltLayer hosted aggregator will be activated upon deployment of the newly deployed AVS.

Next, users can activate the AltLayer-hosted operator to connect to the aggregator. Alternatively, the user can run operator and connect to the aggregator independently.

Finally, Wizard provides an intuitive UI to manage your AVS post-deployment, which includes managing roles, operator whitelisting and updating metadata.