# Architecture Overview

Bound is built on a layered stack where each layer depends on the one below.

## Stack overview

```
┌─────────────────────────────────────┐
│  Layer 3 — Products                 │
│  Launchpad · Lend/Borrow · Options  │
├─────────────────────────────────────┤
│  Layer 2 — Trading Engine           │
│  Runes AMM · SODAX Crosschain       │
├─────────────────────────────────────┤
│  Layer 1 — Infrastructure           │
│  Bound Auth · Bound APIs            │
└─────────────────────────────────────┘
```

## Smart contract stack

Bound uses an EVM environment for AMM calculations, connected to Bitcoin settlement:

```
Client request
    ↓
Sequencer (validate + relay)
    ↓
Relay Contract
    ↓
Bitcoinstate Contract (tracks LP positions, parses to Uniswap format)
    ↓
Uniswap V3 Contract (executes liquidity operations)
    ↓
Bitcoin Node (signs + broadcasts BTC transaction)
```

## Sequencer nodes

Sequencers are nodes operated by Bound and other stakeholders. They:

1. Validate incoming requests (sequence numbers, signatures, data formats, OPCODEs)
2. Forward validated requests to other validator nodes
3. Update state on the EVM chain
4. Co-sign the Bitcoin transaction
5. When consensus is reached, broadcast the final BTC transaction to mainnet

{% hint style="info" %}
**VERIFY** - Bound-specific architecture decisions and rationale to be added by engineering team.
{% endhint %}


---

# 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://bound-1.gitbook.io/bound-docs/protocol-architecture/architecture-overview.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.