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

Operator onboarding

Registry state binds node identity, owner, and active status. Fleet entry is manual/invite-controlled by B3IQ.

Learn More
Receipts and settlement

Signed receipts and payout roots connect completed work to public-safe settlement evidence.

Learn More
Reputation

Uptime, success rate, benchmark freshness, receipt history, payout finality, and dispute outcomes become reputation inputs.

Learn More
Privacy boundary

Public protocol payloads carry hashes, roots, counts, and statuses, not prompts, outputs, keys, exact private routes, or raw TEE material.

Learn More

Registry And Settlement Split

LayerRoleStatus
Node registryNode/model registration, owner binding, active status, and reputation fieldsRegistry tooling and deployments exist
Settlement networkLow-cost operational commitments such as receipt roots, payout roots, availability roots, reputation snapshots, and epoch summariesPayout settlement pilot live

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

Protocol Accountability Loop
authorizedispatchsignbatch Request OpenAI-compatible or private job Route Policy liveness, model, billing gates Node Work eligible runtime executes Receipt signed usage commitment Settlement payout roots + proof logs

Live Explorer

Open b3iq.org/protocol for the current public-safe protocol view. Open explorer.b3.fun when you need the broader B3 network explorer for settlement transactions and account state.

Ask a question... ⌘I