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. The Future

Conclusion

By building the first bridgeless Bitcoin-native application platform, Arch helps developers add programmability while still benefiting from its core strengths of liquidity and security. Its architecture creates novel opportunities to create the next generation of dApps on the world’s most valuable blockchain without sacrificing self-custody and other decentralization principles that are critical to the Bitcoin community.

Last updated 9 months ago