The problem with screenshotted track records
Trading track records are easy to fake. Screenshots of MyFxBook, edited account statements, cherry-picked periods, even the MT5 'Investor password' view can be misleading. Prop firms, investors, and copy-trading subscribers all face the same problem: the track record they are shown is almost impossible to independently verify.
The industry has worked around this with trusted third parties — MyFxBook, FxBlue, the occasional auditor — but these are fundamentally honor-based. They read data from your account and display it. If the third party is compromised or colludes, the record is worthless.
How hash-chain proof works
Algo Studio assigns a cryptographic hash to every trade event the moment it is ingested. Each hash includes the previous trade's hash, so any attempt to edit, delete, or reorder past trades invalidates every subsequent hash in the chain — detectable instantly, without trusting us.
The chain root is published periodically. A third party with the root can verify any trade in the history by recomputing hashes forward from the signed point. Editing a single loss-making trade three months ago is arithmetically impossible without rewriting the entire chain since that trade — and the published roots prevent that.
This is the same primitive that makes blockchains tamper-evident, applied to trade ledgers rather than currency.
Proof bundles for prop firms and investors
A proof bundle is a single JSON file containing the full trade history, the hash chain, signed roots, and the backtest baseline for drift computation. Anyone can download the bundle from a public proof page and run the included verifier (or upload it to /verify on algo-studio.com) to independently confirm the record has not been edited since each trade was logged.
This works for prop firm applications (prove live profitability before applying), investor due diligence (signal providers can share a verifiable track record), and regulatory needs (keep an immutable audit trail).