1. Live intent is logged
Managers submit buy, sell, or rebalance intent. TradeLock records when it was received so the history does not depend on self-reported timestamps.
Verification method
What "Verified by TradeLock" actually means.
TradeLock records live trade intent, timestamps it server-side, captures public market context, and preserves a tamper-evident history for eligible trades. It is designed for credible forward records, not best-execution marketing or HFT analytics.
2. Pricing context is captured
TradeLock anchors the record in public market data and, where available, bid/ask spreads. That creates a more realistic benchmark than a reconstructed mid-price chart.
3. Badge state is shown publicly
If eligible history lines up with the verification model, the strategy can show a Verified by TradeLock badge. If it does not, the public state can degrade instead of pretending nothing changed.
How it really works
TradeLock uses two cryptographic layers to make the record tamper-evident and independently timestamped.
Open the technical breakdown The short version is chained hashes plus a daily Bitcoin anchor. Details
TradeLock uses a two-layer cryptographic design to make the history tamper-evident. The goal is to make unauthorized edits easy to detect, not to claim that no record can ever be challenged.
Layer 1: Internal trade chain
Every logged trade gets a hash. Each new trade also includes the previous trade hash, so the chain is linked end to end. If someone edits or deletes a past trade, that hash changes and every later hash changes too.
Layer 2: Bitcoin anchor
Once a day, TradeLock anchors the latest chain state with OpenTimestamps on the Bitcoin network. That creates an external timestamped checkpoint for the chain that is very hard to rewrite without leaving evidence.
Why it matters
- To rewrite a past trade, the internal chain would have to be recalculated from that point forward.
- The historical Bitcoin anchors would also have to be defeated or replaced.
- Any mismatch between the current chain and the anchored state surfaces as tampering.
The caveat
TradeLock records the price context available at submission, including bid/ask when possible, but it does not model order size, slippage, or market impact. That makes it best for liquid, lower-frequency strategies rather than HFT or thinly traded assets.
Audited brokerage records remain the gold standard. TradeLock is a simpler self-certified alternative for a narrower class of strategies and portfolios.
Important label discipline
Backtested, forward-tracked, and verified are not the same thing.
A backtest shows what a model would have done. A forward-tracked record shows what you actually published going forward. Verified means eligible live activity was recorded through the TradeLock pipeline. CSV imports and sandbox/test data are useful context, but not verification-grade proof.