# Introduction

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfsZs9MLEm6Ng9SIjhOGHiqAylY5KF0aY-H96ooiyfQVK6cyTDZGA6OWgPmDngZgeEqAbUXxyA8I7CYi9anC4Gg8-yRfojjU7TJOK255x0I7vdwdAbcYxgFRyexydepBw2PLQA8eqtBAShveEaWxkqKoVCQ?key=LdTA2DPbhTso83EtzU1n6g" alt=""><figcaption></figcaption></figure>

Arch allows developers to tap into the full liquidity and security of the world’s most decentralized blockchain without forcing their users to bridge.&#x20;

***Arch is not a L2 nor a metaprotocol.***&#x20;

Its core innovation is a novel FROST + ROAST signature scheme that combines with a specialized VM and Validator Network to provide trust-minimized execution. It offers more secure and decentralized utility than bridge-based options, including L2s that sacrifice liquidity for scalability, and meta-protocols, which are limited to state changes but can’t offer the programmatic decentralized asset transfers needed for Turing-complete programs.

Arch’s unique architecture enables trust-minimized programmable multisigs, multi-party computation, cross-program invocations, protocol interoperability, and other elements essential to building the pillars of Bitcoin DeFi, including lending markets, AMMs, and stablecoins.

***Arch does not require any new op codes or soft forks.***

Utilizing Arch's innovative design construct, dApps can now build with the needed flexibility and robustness without necessarily sacrificing self-custody, liquidity and interoperability.

&#x20;Arch makes it possible for Bitcoin users to develop and interact with decentralized applications without taking on additional trust assumptions.&#x20;

\
Discover the future of Bitcoin programs with **Arch Network**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://arch-network.gitbook.io/arch-documentation/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.