​
TOPLOC integration

Status: Planned v1 — not live in production routing or settlement. Signed receipts v0.3 are the live verification primitive today.
Per-request forward-pass attestation for buyer-paid inference. Lineage: TOPLOC (Prime Intellect, 2025).
TOPLOC closes the gap between “the provider signed this output” (receipt) and “this output came from an honest forward pass on the claimed weights” (forward-pass attestation). Malibu cites TOPLOC in the Litepaper as the v1 marketplace verification layer.

​
What receipts do today vs what TOPLOC adds

Do not describe live traffic as “TOPLOC-verified.” Use Security & trust model for current bounds.

​
Planned architecture (high level)

Exact wire format and verifier placement will be documented here when integration ships. Expect:
  • Verifier runs on attested weights aligned with catalog model_hash
  • Failed attestation → settlement fault (same class as invalid receipt)
  • Buyer-visible status distinct from receipt-only valid

​
Failure modes (design-time)

​
Cost and latency budget

Litepaper cites ~1% of serving cost for TOPLOC verification (Prime Intellect, 2025). Latency budget will be published with integration benchmarks on Benchmarks & methodology when v1 ships.

​
Lineage and credit

TOPLOC is not a Malibu invention. Malibu integrates it as the v1 buyer-response attestation layer. Research references live in the repo under whitepaper/research/ when synced.