Protocol Overview
B3IQ protocol accountability across OpenAI-compatible execution, signed receipts, stake, settlement roots, reputation, and disputes.
B3IQ protocol accountability is built from endpoint execution, signed receipts, stake, public-safe route readiness, billing ledgers, payout roots, reputation inputs, challenge jobs, and dispute policy.
The current implementation is not yet a complete production protocol. Base registry tooling, signed receipts, billing ledgers, payout batches, public settlement views, and B3 mainnet payout settlement pilots exist. Full recurring settlement automation, dispute contracts, and production public traffic controls remain roadmap work.
Protocol Primitives
Chain Split
| Chain | Role | Status |
|---|---|---|
| Base | Near-term B3 stake, node/model registry, owner binding, active status, reputation fields, and slashing custody | Registry tooling and deployments exist |
| B3 mainnet | Low-cost operational commitments such as receipt roots, payout roots, availability roots, reputation snapshots, and epoch summaries | Payout settlement pilot live |
Public Protocol Surface
Public protocol payloads may expose:
- Hashes, roots, and counts.
- Public transaction hashes.
- Public node and model IDs.
- Route-readiness blockers and next actions.
- Benchmark summaries and freshness status.
- Settlement totals and payout batch finality.
- Reputation summaries.
Public protocol payloads must not expose:
- Raw prompts or model outputs.
- API keys, customer tokens, local API keys, support secrets, token hashes, or setup tokens.
- Customer identity.
- Exact private routes or raw request logs.
- Local runtime URLs, filesystem paths, private tunnel details, connector tokens, or route secrets.
- Raw TEE quotes or certificate chains.
Current Protocol Loop
Live Explorer
Open b3iq.org/protocol for the current public-safe protocol view.