Every execution doc is written to be readable on its own; this is the lookup for the recurring terms. The plans themselves:
working-plan.md(the hub), thent1-plan.md,t2-plan.md,t3-plan.md, andengineering-calendar.md.
ProofBridge lets two people trade tokens across two different blockchains (Stellar and Ethereum) directly with each other. Each person's money sits in a vault on their own chain, and the vaults only open when a mathematical receipt proves the other side paid. There is no shared pot of money for hackers to drain, which is how most bridge hacks happen. Today it runs on the practice networks; the grant takes it to the real networks.
| Term | Meaning |
|---|---|
| Testnet / mainnet | The practice network with play money / the real network with real money |
| Smart contract | A program on the blockchain that holds and releases money by fixed rules no one can bend |
| Relayer ("the middleman") | The trade-approval service we run today; phase 1 removes it |
| BLS signature | The combined "both of us agree" signature that replaces the middleman — both traders sign, the signatures merge into one, the blockchain checks it |
| ZK proof ("the receipt") | A piece of math that proves a deposit happened, without anyone having to take anyone's word for it |
| MMR / Merkle tree | The on-chain ledger of deposits that the receipt is checked against |
| Maker / bridger | The person supplying money on one side of a trade / the person bridging their tokens across |
| Ad | A maker's standing offer: "I have this much of this token available to trade" |
| Agent ("the bot") | A maker's automated trader, limited by rules the maker sets on-chain — like an assistant with a company card: per-trade cap, daily cap, allowed list, instant cut-off |
| The complaint desk | The dispute system: file with a small bond, the other side responds, a panel decides one of four outcomes |
| Cancel-after-deadline | Any trade stuck past its deadline can be cancelled by anyone; the refund routes automatically to the right person |
| The soak | The 14-day live public test at the end of phase 2 — outside users, real traffic, hands off |
| The audit | The outside security review (via Stellar's Audit Bank) that gates the launch; done in two batches so it fits the schedule |
| Green light | The auditors' written confirmation that all serious findings are fixed — the launch gate |
| Multisig ("shared lock") | Control that needs several keyholders to agree, including people outside the team |
| ArbiterRole | The dispute panel's shared lock: 5 of 7 keyholders, 3 team + 4 outside — every decision includes at least 2 outsiders |
| Timelock ("the 24-hour delay") | Every admin change waits 24 hours in public before taking effect; no quiet rule changes |
| The switchover | The week-5 migration where the old middleman contracts are retired and the new suite takes over |
| First-transaction ceremony | The supervised ~$1 transfers in both directions that prove the live route works before it opens |
| The smoke detector | The reconciliation listener: a watcher on both chains that flags any settlement mismatch within 5 minutes |
| SDK ("the toolkit") | The package other developers use to plug ProofBridge into their own apps |
| USDC | Circle's dollar-backed token, already live on both chains — the launch route bridges it; ProofBridge issues no tokens |
| Deliverable tags (1.1–3.9) | The numbered line items from ../3-submission/submission.md; the quick index is in the scf_docs README |
| T0 / tranche | The kickoff payment / each 6-week milestone with its payment |
| 30-day proof window | The success test after launch: 100+ transfers, 99.5% success, 10+ distinct users — why launch is pinned to week 14 |