- The two traders authorize it. Both parties sign the settlement with their BLS settlement keys. The contracts on each chain check the combined signature against an on-chain key registry. No trade needs ProofBridge’s permission.
- Deposits are proven, not trusted. A payout on one chain carries a zero-knowledge proof that the other side’s deposit really is recorded on the other chain. The destination chain can’t read the source chain; the proof carries that fact across.
- Every trade has an ending. Each order has a deadline. If a trade doesn’t settle by then, it can be cancelled and the deposit refunded, or either party can file a dispute. These paths are part of the contracts, not a support process.
You’re reading the v3 docs: the protocol as it runs on soak, after
the second build tranche. The earlier designs are in the version picker
under v2 and v1 (pre-BLS).
- Mainnet
- Soak
Mainnet isn’t live yet. Use Soak to try ProofBridge today.
What you can do
Bridge assets
Move tokens from one chain to another. Connect a wallet, register your
settlement key once, and trade. No sign-up, no KYC.
Provide liquidity
Post a liquidity ad and earn a fee on every trade against it. Serve
trades yourself, or let an agent lock orders for you within limits you
set.
What’s new in v3
- Fees: 0.3% to the maker and 0.2% to the protocol on each trade (Fees).
- Deadlines, cancels and refunds: every order ends, one way or another (Deadlines and clocks, Cancels and refunds).
- Disputes: either party can file, with evidence (Disputes).
- Your own trade secret: each party derives its half of the secret that unlocks its payout (Trade secrets).
- Agents: an agent can lock orders on your ads, within an on-chain policy you set (Agents).
Where to go next
- How it works: the full trade lifecycle in one page
- Quickstart: bridge your first tokens
- Settlement keys: the key every trading wallet registers once
- Smart contracts: addresses on mainnet and soak