How Do You Prove You Called a Trade Before It Happened?

Why the obvious methods fail

A chat message. Discord and Telegram both allow editing and deletion, usually without a visible trace to a newcomer scrolling back. A channel you administer is a document you control.

A social post. Better — public posts are archived and edits are often flagged — but the standard technique is volume: post many contradictory calls, delete the wrong ones, screenshot the right ones. Nothing about a single surviving post reveals how many siblings it had.

A screenshot with a clock in it. Proves a device displayed something. System clocks are adjustable and images are editable.

The common flaw is that all three are produced and retained by the person making the claim. Proof of prior commitment has to come from somewhere the claimant cannot reach after the fact.

What actually establishes precedence

Three properties, together:

1. A timestamp from a source you do not control. Your own clock is not evidence about your own claim.
2. Sealing. The content is fixed at commit time. Committing a hash rather than the readable text lets you prove later that this exact call was what you committed, without revealing it early.
3. Append-only anchoring. The record as a whole cannot have entries inserted, reordered or removed after the fact — otherwise a complete set of calls can be quietly pruned to a flattering subset.

That third property is the one people miss. Timestamping a single call proves that call is old. It says nothing about the ninety other calls made the same week, and the ratio between them is the entire question.

The time capsule, and why a delay is the point

There is a tension in publishing calls: a call that is public immediately is actionable by everyone, which is precisely what a trader holding a live position cannot afford. A call that is published only after the fact is not proof of anything.

A time capsule resolves it. The commit is sealed at the moment it is made — fixed, timestamped, unmodifiable — but not readable until the delay expires. The record is the trader's to share, with whoever they choose; the public proof appears when the capsule opens. So the trader is not choosing between proving the record and keeping a position private while it is live.

Merkle anchoring in one paragraph

Each sealed commit is hashed. Those hashes are combined pairwise into a tree until a single root hash remains, and that root is written to Hedera. Changing any commit changes its hash, which changes every hash above it, which changes the root — and the old root is already published. So the tamper is detectable by anyone, without needing access to kappi's database or trusting kappi's word. Adding a trade later is equally visible, which is what makes the record complete rather than merely authentic.

What this proves and what it does not

It proves the call existed, in that exact form, at that time, and that the surrounding record has not been pruned. It does not prove the call was good — a timestamped bad call is still a bad call, permanently. Traders sometimes discover that they want proof of precedence rather less once it applies to everything they say.

Broker-import journals prove what you did after the fact, from data you control. kappi timestamps what you said you would do, before you knew how it would turn out, on a record you cannot edit.

Is proving precedence a solved problem?

It has been solved since 1991. Haber and Stornetta's paper set out how to time-stamp a digital document so that neither the author nor the timestamping service can forge the date, by hashing each document and linking the hashes into a chain^[1] — the construction later generalised into hash-linked ledgers. The IETF standardised a version in 2001 as RFC 3161, in which the authority signs only a hash of the data and never sees the data itself.^[2]

That second detail is the one traders should notice. Proving a document existed at a time has never required disclosing what it says. A sealed commit is that thirty-year-old property applied to a position instead of a contract.

kappi is a trade recorder: you commit a trade before the fact, it is sealed on your device for a time-capsuled delay you choose, and published afterwards on a Merkle-anchored log a reader can check without kappi's cooperation. $15/month, no free tier.