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
  1. Rollup Types

Flash Layer Rollups

PreviousSecurity via Fraud ProofNextExample Use cases

Last updated 1 year ago

A persistent issue for blockchains has always been scalability. We frequently see cases of a single dApp's sudden surge in popularity bringing the entire network close to a halt. The fundamental cause of such scalability issues is the idea and practice of running all the dApps on a single monolithic blockchain.

Some of the common causes of a large surge in usage include but is not limited to token sales, play-to-earn game events and airdrops. A common trait among these causes is that they are relatively independent and are transient in nature. In light of this, AltLayer provides a unique rollup called FlashLayer.

Flash layers are disposable application-tailored rollups with optional fraud proofs.

With Flash Layers, a dApp developer expecting an increase in demand for his application could: 1) quickly spin up a fast and scalable rollup secured by a Layer 1, 2) use the rollup for as long as needed and thereby prevent clogging of the Layer 1, and then 3) dispose of the rollup by doing an “end-of-life” settlement on the Layer 1. This makes the entire system highly resource-optimised. The execution layer and its resources are called upon only when the dApp expects a considerable demand that a Layer 1 can’t handle and once the demand tapers off, the dApp can move back to the Layer 1.

Flash Layer provides an elastic burst of capacity in the form of a transient execution layer secured by an underlying chain. Rather than building a custom chain for a specific event or to deploy the contract on the Layer 1 itself, the event administrator may signal the demand for a transient burst of compute capacity. This in turns creates a FlashLayer specific for the dApp with the appropriate state and asset bridging facilities. At the end of the signaled duration, the states and assets of the FlashLayer are rolled-up onto the underlying Layer 1 chain and the FlashLayer is disposed off with all its resources freed.