How trust works

Why you can believe the numbers here.

Anyone can post a screenshot of profits. TrueFills is built so that a verified strategy has no way to fake one: its record is read from its broker, so there is no version of events for its owner to write. Three simple ideas do the work.

1. 1. The broker speaks, not the trader

   Once a strategy links the brokerage account it trades, its numbers come straight from that brokerage, the way a bank statement comes from the bank. Its owner never gets to report their own results, and neither do we. That is a stronger promise than catching a liar after the fact: there is simply nothing for them to write.

   A new strategy can start posting through the API before it links an account, so it can begin building a history on day one. Until it links one, it is labeled unverified on every screen it appears on, and you should read it as a claim rather than a record.

2. 2. History is written in ink

   Once a day is recorded, it stays exactly as it was, forever. A losing day cannot be quietly deleted, a drawdown cannot be smoothed over, and a start date cannot be moved to hide a rough beginning. What happened is what you see.

3. 3. Every day gets a seal anyone can check

   At the end of each trading day, the record is stamped with a unique digital seal, and each seal is built from the one before it, like links in a chain. Change even one number in the past and every seal after it visibly breaks. The whole chain is public on the registry, and the verify page lets your own browser re-check every link with one click. You never have to take our word for it.

Questions

Where do the numbers come from?

For a verified strategy, straight from the broker that holds the account. Balances, positions and trades are pulled automatically every day, and the strategy owner never gets to type any of it in. A strategy that has not linked a brokerage account yet is a different matter: its bot posts its own trades, nothing confirms them, and it is labeled unverified everywhere it appears.

How do I know which kind I am looking at?

Every strategy carries its label at the top of its page. Unverified means no brokerage account is linked and nothing has been checked. Verified against a simulated account means the trades are real records of practice money. Verified against a funded account means real money. Which of the two it is comes from the broker's own marking of the account, not from what the creator calls it. Only funded strategies are allowed to charge for subscriptions.

What happens if an unverified strategy links an account later?

We check what it claimed against what the broker shows, and publish the result on its page: how much of the claimed history the broker confirms, any trades the broker shows that were never disclosed, and any trade posted long after it happened. Nothing gets quietly upgraded.

What stops a record from being edited later?

History here works like ink, not pencil. Each day is written once and can never be changed or deleted. On top of that, every day gets a digital seal that depends on all the days before it, so touching anything in the past visibly breaks every seal that came after.

Can I check it without trusting this website?

Yes. The full sealed history is public, and the verify page lets your own browser re-check every seal with one click. Our servers get no say in the verdict.

What does verification NOT prove?

The seals prove the history is genuine and untouched. They do not predict future returns, and they cannot make a bad strategy good. Backtested figures remain simulations and are always labeled as such.

What is the difference between live and backtested numbers?

Live numbers come from a brokerage account trading in real time and are part of the sealed record. Backtested numbers are simulations over historical data, shown for context and always labeled. A backtest is never verified, however good it looks.

Trading involves risk of loss. Past performance, live or simulated, does not guarantee future results. Curious about the technical details? They live in the API reference.