> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pfbridge.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction to ProofBridge: P2P Cross-Chain Bridge

> ProofBridge is a peer-to-peer cross-chain bridge secured by zero-knowledge proofs. Move assets across chains with no custodians or centralized relayers.

ProofBridge lets you transfer assets between blockchain networks by connecting directly with a counterparty — no centralized custodian holds your funds, and no trusted committee approves your transaction. Settlement is enforced entirely by cryptographic proofs verified on-chain.

## What you can do with ProofBridge

ProofBridge supports two roles. You can use ProofBridge as a **Bridger** when you want to move assets from one chain to another, or as a **Maker** when you want to earn by providing cross-chain liquidity.

<CardGroup cols={2}>
  <Card title="Bridge assets" icon="arrow-right-arrow-left">
    Deposit tokens on one chain and receive equivalent tokens on another. No registration, no KYC — just connect your wallet.
  </Card>

  <Card title="Provide liquidity" icon="droplet">
    Post a liquidity ad on your chosen chain and earn fees whenever a Bridger uses your liquidity to settle a transfer.
  </Card>
</CardGroup>

## Key benefits

**Trustless settlement.** Funds are released only after a zero-knowledge proof confirms both sides of the trade are valid. Neither party can take the other's funds without completing their end of the deal.

**Peer-to-peer matching.** Bridgers and Makers interact directly through on-chain contracts. There is no bridge operator controlling liquidity pools or deciding which transfers to process.

**No registration required.** Signing in with your wallet is all the authentication you need — either via Sign-In With Ethereum (SIWE) for EVM wallets or a Stellar wallet signature.

**Non-custodial.** Your tokens are locked in auditable smart contracts, not held by a third party. The contracts release funds only when the ZK proof passes on-chain verification.

## Supported networks

ProofBridge is currently live on the following testnets:

| Network          | Chain ID | Role                        |
| ---------------- | -------- | --------------------------- |
| Ethereum Sepolia | 11155111 | Source or destination chain |
| Stellar Testnet  | 1000001  | Source or destination chain |

<Note>
  Stellar does not have a native numeric chain ID — `1000001` is the internal identifier ProofBridge uses to distinguish Stellar Testnet inside the relayer and frontend. The canonical Stellar network identity is the passphrase `Test SDF Network ; September 2015`.
</Note>

<Note>
  ProofBridge is currently deployed on testnets. Mainnet deployments are on the roadmap. Use testnet funds only.
</Note>

### Active bridging routes

The live routes for native token bridging are:

* **ETH (Sepolia) ↔ wETH (Stellar)** — ETH is automatically wrapped to WETH on deposit and unwrapped on withdrawal. The Stellar side uses a SEP-41-compatible contract.
* **XLM (Stellar) ↔ wXLM (Sepolia)** — XLM is automatically wrapped to WXLM on deposit and unwrapped on withdrawal.

## The two user roles

### Bridgers

A Bridger is any user who wants to move assets from one chain to another. You deposit tokens on the source chain using the **OrderPortal** contract. Once the deposit is confirmed and a ZK proof is generated, you receive the equivalent tokens on the destination chain — all without trusting an intermediary.

### Makers

A Maker is a liquidity provider. You post a **liquidity ad** on a chain using the **AdManager** contract, specifying how much liquidity you want to offer and at what rate. When a Bridger selects your ad and completes a deposit, the ZK proof system releases your destination-chain liquidity to the Bridger and sends the Bridger's source-chain tokens to your designated address.

<Info>
  You do not need to choose a role permanently. The same wallet can act as a Bridger on one trade and a Maker on another.
</Info>

## Why we're building ProofBridge

Cross-chain bridges have lost more than \$2B to hacks, almost all of them targeting the same architectural weak point: a trusted multisig, validator set, or relayer that custody user funds mid-transfer. ProofBridge replaces that trust boundary with cryptography — users prove their own deposits, funds never leave on-chain escrow, and the relayer can only submit proofs the contract independently verifies.

<Card title="Read the full problem statement and solution" icon="shield-check" href="/why-proofbridge">
  The security failures we're designing away, the dual authentication model, and the end-state design with BLS signature aggregation.
</Card>

## What's on the roadmap

ProofBridge is live on testnet with a single relayer coordinating settlement. That single-relayer dependency is a transitional bootstrap, not the end state. Planned upgrades include:

* **BLS signature aggregation** for a decentralized relayer set, removing the last trust assumption.
* **AI automation layer** for anomaly detection, automated order matching, and a Maker/Bridger co-pilot that can act inside scoped, user-authorized bounds.
* **More chains**: Arbitrum, Base, Optimism, Polygon, Starknet, and Solana.

<Card title="See the full roadmap" icon="map" href="/reference/roadmap">
  Phased rollout from testnet to mainnet, BLS aggregation milestone, and the AI agent enhancement design.
</Card>

## Where to go next

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Connect your wallet and make your first bridge transfer in a few steps.
  </Card>

  <Card title="How it works" icon="circle-info" href="/how-it-works">
    See the full end-to-end flow, from liquidity ads to ZK-proof settlement.
  </Card>

  <Card title="Run it locally" icon="docker" href="/contribute/run-locally">
    Bootstrap the full stack on your machine with one command.
  </Card>

  <Card title="Compared to other bridges" icon="scale-balanced" href="/concepts/comparisons">
    How ProofBridge differs from CCTP, Houdini Swap, and validator-based bridges.
  </Card>
</CardGroup>