Protocol Overview
B3IQ protocol accountability across OpenAI-compatible execution, signed receipts, operator onboarding, settlement roots, reputation, and disputes.
B3IQ protocol accountability is built from endpoint execution, signed receipts, operator onboarding, public-safe route readiness, usage records and payout ledgers, reputation inputs, challenge jobs, and dispute policy.
The current implementation is not yet a complete production protocol. Registry tooling, signed receipts, usage records and payout ledgers, payout batches, public settlement views, and payout settlement pilots exist. Full recurring settlement automation, dispute handling, and production public traffic controls remain roadmap work.
Protocol primitives
Registry state binds node identity, owner, and active status. Fleet entry is manual/invite-controlled by B3IQ.
Signed receipts and payout roots connect completed work to public-safe settlement evidence.
Registry and settlement split
| Layer | Role | Network | Status |
|---|---|---|---|
| Node registry | Node/model registration, owner binding, active status, and reputation fields | Base mainnet (8453) | Registry tooling and deployments exist |
| Settlement network | Low-cost operational commitments such as receipt roots, payout roots, availability roots, reputation snapshots, and epoch summaries | Base mainnet (8453); earlier batches on B3 (8333) | Payout settlement pilot live |
Both layers settle on Base mainnet, where anyone can read them without our cooperation: registration so a third party can check a node independently, and payout proofs so a batch root can be verified against the amounts it commits to.
Payout proofs ran on B3 mainnet (an OP Stack L3 that settles to Base) during the pilot, and batches finalized then are still proved there. Each batch records the chain it was broadcast to, so an older proof stays verifiable on the network that actually holds its transaction.
Neither is the payment surface. Owner payouts are denominated and paid in USD; see Receipts and settlement for what is published and how to verify it.
Public protocol surface
Public protocol payloads may expose:
- Hashes, roots, and counts.
- Public settlement 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 for the current public-safe protocol view: live receipt, settlement, and node-readiness counts, with per-node detail under b3iq.org/nodes. Open explorer.b3.fun when you need the broader B3 network explorer for settlement transactions and account state.