BTA / Delivery desk
Timestamp Proof vs Alert Delivery Proof
A verified commitment, a screen receipt and a broker response authenticate different objects.
Inspect the committed bytes
A timestamp proof concerns a specific committed object. Ask which fields and representation were included and retain the original artifact. A label saying timestamped should not extend protection to fields outside that object. Changes to uncovered instructions still need their own versioned evidence.
Verification must distinguish a pending submission from a completed attestation. A self-reported event time inside committed data is not independently proven as the exact time the event happened. A completed proof can support existence of the covered bytes by its attestation boundary; it does not fill every earlier event-time gap.
Do not borrow the proof for another stage
A commitment does not inherently establish dispatch to a particular destination. A transport acknowledgement does not inherently establish display to a person. A displayed message does not inherently establish an accepted order. Each stage needs its own original record and meaning. A chain is not complete because one stage has a strong proof.
Keep a provenance map that names the object, covered fields, verifier and conclusion. Where delivery or account evidence is absent, report the absence. This prevents a technically correct statement about a commitment from becoming a misleading marketing statement about the entire trading workflow.
Make verification reproducible and bounded
Retain the safe original artifact and completed verification result where a test actually occurs. Redact secrets without claiming the altered public object has the same proof. If the reader cannot reproduce the verification, label the result attributed rather than independently checked by BTA.
The publication's documentary notes explain what a receipt can establish. They do not claim a new independent verification of every publisher object. A buyer still needs the exact instruction history, destination observations and account records relevant to the claim under review.
Original Evidence Packet
| Artifact | Record to retain |
|---|---|
| Commitment | Original object and explicitly covered fields |
| Attestation | Pending/confirmed state and verifier result |
| Other stages | Separate delivery and order records |
Continue the Investigation
Source Boundaries
Official references describe published mechanisms. BTA's evidence packets and proposed test procedures do not claim a completed paid-feed or account trial.