Reputation And Disputes
B3IQ reputation inputs, challenge jobs, disputes, non-slash defaults, and future slashing boundaries.
B3IQ reputation should be evidence-led. A node earns trust from public-safe signals such as route readiness, successful receipts, benchmark freshness, health history, payout finality, and dispute outcomes.
Reputation Inputs
| Input | Meaning |
|---|---|
| Uptime | Fresh heartbeat, online history, route health, and tunnel health |
| Benchmark freshness | Control-plane-observed benchmark evidence and stale-proof prompts |
| Success rate | Accepted work, failed dispatches, router errors, and receipt acceptance rate |
| Receipt count | Volume of completed work with signed evidence |
| Payout finality | Payout rows batched and finalized through settlement evidence |
| Dispute rate | Challenge outcomes, appeal status, and validated failures |
Dispute Defaults
B3IQ should prefer non-slash paths before slashing:
- Refund customer.
- Release reservation.
- Withhold payout.
- Suspend node or profile.
- Lower reputation score.
- Require fresh benchmark or attestation.
- Escalate to operator review.
Slashing should only happen when policy clearly defines the violation, the evidence standard, the decision path, and the appeal window.
Challenge Jobs
Challenge jobs can support disputes without exposing raw customer prompts or outputs. Public-safe evidence can include:
- Challenge class.
- Node and model commitment.
- Expected evidence hash.
- Observed result hash.
- Timestamp and receipt hash.
- Decision reason string.
- Appeal state.
It should not include raw prompts, raw outputs, customer IDs, API keys, exact private routes, or raw TEE material.
Snapshot Shape
Future b3iq-reputation-snapshot-v1 summaries can include uptime, benchmark
freshness, success rate, dispute rate, receipt count, payout history, and
operator status. Raw logs and sensitive payloads stay off public chain surfaces.
Today, public reputation is mostly route readiness, receipt history, health history, benchmark evidence, and payout finality. Full dispute contracts and slashing paths are future protocol work.