Attestation Gateway

Attestation Gateway

Client-side proof generation is only half the loop. Allocators and vaults need a trust anchor that confirms a submitted artifact is valid—without receiving the private witness.

Gateway responsibilities:

• Accept a proof bundle and its public claim (threshold, period, commitment hash)
• Verify the proof against the claim at the API boundary
• Reject stale, mismatched, or below-threshold submissions before they reach capital systems
• Issue a signed attestation receipt that downstream applications—Smart Vaults, allocator dashboards, compliance tooling—can ingest without re-running the prover

Trust model:

• The quant never uploads trade-level data—only the proof and public scorecard fields
• Attestations are time-bounded and nonce-protected to prevent replay
• Signed receipts bridge Phase 1 (proof) to Phase 2 (liquidity): a vault opens deposits only when the attestation clears

The gateway is the airlock between private execution and pooled capital.