Receipts And Settlement
Signed receipts, payout batches, settlement roots, B3 mainnet payout proofs, and public-safe commitment boundaries.
Receipts and settlement turn completed work into public-safe evidence without publishing private payloads.
Receipt Commitments
Receipts can commit to:
- Node ID.
- Model ID.
- Usage totals.
- Price and billing references.
- Receipt hash.
- Receipt status.
- Optional attestation hash for future verified-confidential jobs.
Receipts must not publish raw prompts, model outputs, customer identity, API keys, customer tokens, exact private routes, raw request logs, or raw TEE quotes.
Payout Batches
Payout batches aggregate node payout rows into a public-safe root. The batch can include counts, total amount, merkle root, transaction hash, block reference, status, and timestamps.
| Field | Public-safe? | Notes |
|---|---|---|
| batch_id | Yes | Opaque batch identifier |
| payout_count | Yes | Number of payout rows included |
| total_amount_wei | Yes | Aggregate amount only |
| merkle_root | Yes | Commitment root, not raw private metadata |
| transaction_hash | Yes | Public chain transaction reference |
| customer_id | No | Keep customer identity out of public settlement payloads |
| prompt/output | No | Never include raw request or response content |
Current Settlement Pilot
The B3 mainnet B3IQSettlement payout-proof contract emits canonical payout
batch proof logs. The control plane can finalize payout batches from real chain
receipt evidence.
textB3 mainnet B3IQSettlement: 0xE284b4A03eAaFE1Fb97F8E297f1A77c7330D6d04
The address above is the current B3IQ settlement pilot contract reference from repo deployment metadata. Treat contract addresses as chain-specific and verify with the explorer before operational use.
Settlement Flow
Accept receipts
Completed work submits signed receipt evidence to the control plane.
Create payout rows
Billing settlement creates immutable customer debit and node payout evidence.
Batch payouts
Pending payout rows are batched into a public-safe root with aggregate totals.
Submit proof
The payout batch root is submitted to the settlement contract and emits a public proof log.
Finalize control-plane state
The control plane verifies configured contract/event evidence before marking rows settled.
Roadmap
B3 mainnet payout proof deployment and real payout batch finalization exist.
Automate batch creation, submit, verify, finalize, and recovery paths.
Add receipt roots, availability roots, reputation snapshots, and epoch summaries after formats stabilize.