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. USE CASES

How Arch Unlocks the Core Pillars of DeFi

PreviousHow It WorksNextUsing multi-party programs to enable AMMs, LPs, and DEXs

Last updated 8 months ago

Despite significant innovations in recent years, programmability on Bitcoin has had significant limitations. In order to buy, sell, and exchange assets without giving up custody, Bitcoin-native marketplaces have previously been limited to basic trading of non-fungible assets like Ordinals. Indexers have few command options, which has made it impossible to form non-custodial DEXs for fungible tokens, such as BRC-20 and Runes.

By enabling Turing-complete programs on Bitcoin, Arch lays the foundation for a fully-functioning DeFi system on the world’s most valuable blockchain.

💵Using multi-party programs to enable AMMs, LPs, and DEXs