What Forecast Library proves—and what it cannot
Trust comes from precise claims. A receipt proves integrity of a sealed payload; an optional blockchain attestation adds public timing evidence. Neither proves that a forecast is true or accurate.
Last updated 28 August 2026
Integrity
The Library recomputes the canonical SHA-256 digest of a receipt payload. A match shows that the displayed payload has not changed since it was sealed.
Optional public proof
A per-receipt blockchain attestation can independently anchor the receipt digest and publication timing. Proof is optional and is never presented as proof of accuracy.
Evaluation
A forecast is evaluated only after its target horizon matures and the governed observed outcome is available. Corrections are append-only and never silently overwrite the original record.
Security and reporting
Public clients have read-only access to explicitly public Firestore namespaces. Publishing, proof issuance, signer state, and operational records remain server-controlled through Google Cloud IAM.
Report security or data-integrity concerns to support@ipulseai.com.