Cryptographic receipts and model claims
Integrity of a committed payload is not proof of a model's training or returns.
What was committed?
Inspect the exact message layout, encoding and proof. A visible output may contain more fields than its hash input. Changing a field outside that payload need not change the commitment; do not promise otherwise.
When was it confirmed?
Initial calendar submission is not confirmed Bitcoin attestation. Verify the actual proof and separate its anchoring time from the provider's declared time, delivery and account execution. A timestamp written inside a payload is not independently certified as the moment of prediction.
What remains outside the proof?
A matching digest does not establish architecture, feature causality, complete prediction counts or profit. Model weights, data and experiment manifests need their own identities and checks. One verified instruction must remain one example, not an audit of all outputs.
Sources
- QuantConnect optimization parameters
- ALFRED real-time and vintage data
- OpenTimestamps protocol documentation
Research guides
AI data leakage and holdout audit
Audit feature availability, outcome overlap and test exposure with a frozen experiment record and a worked calendar-boundary example.
Backtest, forward and live evidence
Reconcile simulated decisions, prospective instructions and account fills without promoting one evidence layer into another.
Algorithmic versus AI signal claims
Map fixed rules, trained predictions, AI explanations and order routing to the specific consumer evidence each needs.
A model claim can exceed committed bytes
In a fictional record, a payload commits a generic entry and category but omits model weights, preprocessing and the producing version. A matching attestation cannot establish those missing identities. The reviewer keeps the original bytes and separately requests the experiment manifest. A pending submission also cannot establish that the payload existed before an earlier outcome.
Preserve the proof's actual verified bound instead of relying on the provider-declared time inside its input. One checked receipt is one checked object, not certification of the entire decision population. No real receipt is reproduced by this page. Hash integrity, causal model evaluation and account execution remain different questions with different sources.