Arch Documentation
  • ♾️Introduction
  • πŸŒ‰History of Bitcoin Programmability
    • The Challenges Facing Bitcoin DeFi
  • Bitcoin-Native vs. Bitcoin L2s & Metaprotocols
    • Why L2s and Meta-protocols Aren’t Enough
  • πŸ”—Quick Links
  • FUNDAMENTALS
    • 🌟Introducing Arch
      • Arch’s Signature Scheme Model (FROST + ROAST)
      • How Arch Works
      • Bridgeless Execution
      • Decentralized Validation
      • State Transitions Anchored on Bitcoin
      • Minimized Trust Assumptions
    • Step-by-Step User Journey on Arch
      • How It Works
  • USE CASES
    • How Arch Unlocks the Core Pillars of DeFi
    • πŸ’΅Using multi-party programs to enable AMMs, LPs, and DEXs
      • 🀝Example: A Bitcoin DEX
      • πŸͺ™StableCoin
  • DEVELOPERS
    • Overview
    • FAQ
  • The Future
    • πŸ—ΊοΈRoadmap
    • πŸ”ŽAudits
Powered by GitBook
On this page
  1. FUNDAMENTALS
  2. Introducing Arch

Bridgeless Execution

Unlike L2s and meta-protocols where users must bridge or wrap their assets and then send the assets to a smart contract, Arch allows users to send their assets directly through the smart contract invocation without bridging or wrapping first.

All asset transfers can occur using native bitcoin transactions involving UTXOs, although account-based systems such as Layer 2s can also be built using Arch (to optimize transaction speeds as high-performance chains do, for example).

PreviousHow Arch WorksNextDecentralized Validation

Last updated 9 months ago

🌟