What an On-Chain Proof Can Establish
A confirmed proof has a narrow byte-identity and time-bound meaning.
Check the Receipt
Identify the exact preimage, hash and confirmed attestation before stating a time bound. A declared publication field is not external proof of delivery. Pending calendar submission must not be presented as completed Bitcoin confirmation.
Do Not Extend the Claim
Uncommitted fields, excluded instructions, private message delivery and exchange fills need separate evidence. One valid receipt cannot certify an entire strategy history. Never publish secret salt or account information merely to make an example look transparent.
Primary Sources
A proof starts with the included object
A digest can bind exact bytes under its proof mechanism; the claim remains limited to those bytes and that mechanism. First identify the canonical message encoding and which fields are actually included. A later display can add an exit, quantity or friendly asset name without putting it into an earlier payload. Keep publication, calendar submission, completed attestation and receiver arrival distinct. This desk has not independently verified a real private receipt. Detailed proof vocabulary therefore does not establish an actual account's timing, complete historical population or economic outcome.
Crypto assets and Bitcoin timestamps are different topics
Using Bitcoin for a timestamp mechanism does not mean a provider trades Bitcoin, supports a particular token or supplies an exchange route. Trading scope needs its own product documentation. Likewise, an on-chain token transfer is not automatically a derivative execution or proof of profitable strategy economics. Preserve chain, asset, transaction and account scope before interpreting it. The inverse teaching calculation produces fictional coin settlement under declared labels; it is not an on-chain transfer, live wallet balance or authenticated venue event. No asset entitlement is inferred from the proof technology.
Missing fields cannot be reconstructed by confidence
A payload without fee, funding, executed quantity and valuation lacks those economic objects even if the digest check succeeds. A supplied candle after the signal cannot reconstruct actual receiving liquidity or original arrival. A selected successful receipt cannot show complete eligible history without a population contract. Ask for the omitted fields and their original sources. Keep unknown states rather than inserting plausible fills. The paper outage drill demonstrates why message identity, execution identity and current position state must stay separate; its authored sequence does not verify any real customer event.
Use a narrow proof checklist
Identify the original payload, encoding, digest, proof file, completed verification result and source scope. Preserve an exact error when a proof cannot be verified. Separately request full model history and receiving-account reconciliation. These tasks are not interchangeable, and a teaching worksheet performs neither. The publication presents no fake audit seal, customer testimonial or independently witnessed proof pair. TODO(Darren): supply authentic payload/proof examples and complete performance records before the profile can state independently checked timing or economics beyond the included message fields.