> ## 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.
# Overview
> How ProofBridge is built today, where it's going, and how each phase upgrades the trust model — with per-phase architecture diagrams.
ProofBridge is built as a sequence of phases, each tightening the
trust model and expanding what the protocol does without changing
its core peer-to-peer-with-ZK-proof foundation.
Each phase carries a status marker — ✅ live (deployed on testnet
or mainnet), 🔨 planned (in the current Build Award), or 📅 follow-up
(separately scoped, post-mainnet).
## The five phases
✅ **Live on testnet.** Bridge transactions settle today between
Sepolia and Stellar Testnet. A ZK proof gates every unlock; a
pre-auth relayer sits in front of every call as transitional
scaffolding.
🔨 **Planned for T1.** Stateless BLS12-381 aggregation replaces
the trusted relayer. Maker and bridger each sign once; their
combined signature joins the existing ZK proof at every unlock,
and anyone can submit the call.
🔨 **Planned for T2.** Soroban custom-account agents act under
scoped policy without holding wallet keys. Order deadlines unlock
permissionless cancel paths; contested orders flow through a
bonded dispute lifecycle.
🔨 **Planned for T3.** Audit-gated launch on Stellar + Ethereum
mainnet over USDC ↔ USDC. Admin and `ArbiterRole` move to
multisigs with a 24-hour timelock; the 0.5% protocol fee turns
on (0.3% to LPs, 0.2% to the protocol).
📅 **Follow-up tranches.** DAO governance over the arbiter,
slashable agent stake, more chains, and RWA route partnerships
— all post-mainnet.
## End-state architecture (Phase 4)
The diagram below is the shape ProofBridge takes at the end of
T3. Earlier-phase diagrams have fewer actors and contracts —
click into each phase for the snapshot at that point.
Read the diagram top-down:
* **Top row** is actors. Makers, bridgers, and agents are
end-users. The admin and arbiter multisigs are the protocol's
remaining trust anchors — bounded, transparent, and on-chain.
* **Middle rows** are protocol contracts. `AdManager` and
`OrderPortal` are the two escrow contracts users interact with.
`Agent Account` and `Timelock` are gateways that gate calls
rather than holding funds. `MerkleManager`, `BLSKeyRegistry`,
`Verifier`, and `Fee Pool` provide supporting state.
* **Bottom** is the reconciliation listener — an off-chain HA
service that watches both chains and alerts on settlement
discrepancies. It has no on-chain authority.
Every contract on the diagram exists on both Stellar (Soroban)
and Ethereum (Solidity); the same shape mirrors across chains.
## What each phase changes
| Phase | Trust model change | Capability change |
| ------- | ----------------------------------------------------------- | ------------------------------------------------------- |
| Phase 1 | Single-key admin + trusted relayer | Bridging works; relayer is a liveness bottleneck |
| Phase 2 | Pre-auth retired; aggregator becomes untrusted | One signed message per user, used on both unlocks |
| Phase 3 | Agents act under policy; arbiter resolves disputes | Automated maker liquidity ops; stuck orders recoverable |
| Phase 4 | Admin = multisig; arbiter = separate multisig; 24h timelock | Mainnet-ready; protocol fees live; USDC route active |
| Phase 5 | Multisig → DAO governance; agents post stake | Decentralized arbitration; slashable misbehavior |
Click into any phase for the contract-level delta vs the prior
phase and the diagram for that snapshot.
## Where to read more
The current 12-step cross-chain flow as it actually runs on
testnet. Useful baseline before reading the planned phases.
Trust assumptions in the current phase and how they shrink
through Phases 2–5.
Per-contract reference: AdManager, OrderPortal, MerkleManager,
Verifier — function signatures and storage.
The chronological / when-does-what view of the same phases.