Proof certification

What “Verified by Tradoshi” means

Anyone can post a screenshot of a nice profit. Nobody can prove they held their own rules thirty days straight, nor show a profit factor computed over an imposed period, every trade included, with the trade count written on it. That is what Tradoshi certifies. This page explains how, and what the certification does not say.

What we certify: two families

A behaviour, or a result. Never an amount.

A Tradoshi proof carries no sum. No balance, no capital, no profit in euros. The first family certifies how someone works; the second certifies a result, but as ratios and percentages, and under three conditions that are not negotiable.

A profit proves nothingA trader who bets their whole account sometimes wins. The screenshot is true and the information is worthless. A loss limit held for thirty days cannot happen by luck, and neither can a profit factor over two hundred trades.
What changes everything: the window is imposedA result can be framed. A performance proof therefore covers a closed calendar period, picked from a list, never two free dates. Every trade closed on the account goes in, no filtering by instrument or strategy, and the trade count is published with the badge and written into the fingerprint.
A losing trader can publish oneThat is the deciding test, and it holds for both families. A discipline proof can be shared even in a bad week. A profit factor of 0.84 is published exactly like one of 1.60: refusing the bad numbers would turn the whole platform into a winners' filter, which is the very bias we claim to fix.

Showcasing figures is performance promotion, which is regulated ground. Tradoshi is a journalling tool, not a financial service: publishing only ratios and percentages, never an amount or a return, and carrying the regulatory notice on every image, is what keeps this out of that scope.

The nine proofs, and their exact criterion

Each one is computed on the account's own trades. Nothing is declared by the trader, nothing is typed in by hand.

Six discipline proofs

🛡️30 days without breaking their daily limit30 consecutive trading days under their daily loss limit.
🎯50 trades in a row with a stop50 consecutive trades entered with a stop loss set.
⏱️90% of trades inside their own hoursOver 30 days, 90% of trades opened inside their declared windows.
📒100 trades journaledKeeping the journal, 100 trades long.
🏦Prop firm challenge passedA challenge taken all the way to a funded account.
👑Funded account held without a breachHolding a funded account at least 3 months with no breach.

Three verified performance proofs

On a single account, live and synced from the broker, over a closed calendar period. The badge carries the period and the trade count: a rate without its denominator is a claim, not a measurement.

⚖️Verified profit factorGross profit divided by gross loss, over a closed calendar window, every trade on the account.
📉Maximum drawdown heldThe deepest fall from a peak, as a percentage, across the whole window.
🧮Verified win rate and payoffThe win rate AND average win over average loss, never one without the other.

These criteria are identical in the app, on each proof's public page and on this page. A criterion stated here and measured differently elsewhere would be the one lie this system cannot afford.

How it is certified

Four steps. Once the proof is issued, nothing further depends on us.

  1. The maths is redone by our serversThe trader's browser only asks for a badge. Our servers read their history back, redo the calculation with the same engine as the app, and refuse if the criterion is not met. What a browser sends, a browser can make up.
  2. The proof gets a unique IDIn the form TDS-XXXX-XXXX. It is deliberately not sequential: an incrementing number would let anyone enumerate the base and count how many proofs exist.
  3. A fingerprint is computedA SHA-256 of seven fields: the format version, the ID, the badge, a pseudonym for the trader, the value reached, the date, and where the data came from. No email and no broker account number appears in it, or ever leaves our servers.
  4. The fingerprint is written to a public chainOne transaction on Base, an Ethereum layer 2, one per badge. The transaction's data field is exactly the fingerprint shown on the page. Nothing else is written there: a public chain is public forever, and nothing can be taken back.

What anchoring proves

  • That this fingerprint existed at the transaction date, timestamped by a third party we do not control.
  • That Tradoshi backdated nothing and manufactured nothing afterwards. We hold the database: without anchoring, you would have to take our word for it.
  • That the proof was indeed issued, even if its author withdraws it later. The transaction cannot be erased.

What it does not prove

  • Nothing about the quality of the data that went in. A fingerprint is blind to what it seals.
  • Nothing about money. No proof covers a profit, an account size or a return.
  • Nothing about the future. A disciplined trader can still lose money, which is exactly why discipline is measured separately.

The limit we would rather state ourselves: cryptography does not look at where the numbers came from. A fabricated statement, once imported, would produce a technically flawless proof. That is why every proof shows its PROVENANCE in plain words — live account synced from a named broker, demo account, or statement imported by hand — on the public page and on the shared image alike. A badge earned from an uploaded file must not read like a badge earned on a live account, and it is for the reader to judge.

Earned or composed: two objects, and it shows

The app produces two kinds of image. Only one of them is a certification.

Earned proof

  • Triggered by measured behaviour, never chosen.
  • Carries “Verified by Tradoshi”, an ID, a public page and a transaction.
  • Recomputed by our servers before being issued.

Composed card

  • The trader picks which metrics to show.
  • Carries “Generated by Tradoshi”, and attests to nothing.
  • No ID, no page, no anchor.

The distinction is structural, not cosmetic. If everything said “verified”, nothing would be, and the first false proof under our logo would destroy the value of every other one.

Checking a proof someone sent you

Three minutes, no account, and no need to trust us.

  1. Open the address printed on the imageIt looks like tradoshi.com/p/TDS-XXXX-XXXX. If the image carries no address, it is not a certified proof.
  2. Read the provenance before the numberLive account synced from a broker, demo account, or imported statement: that line decides what the rest is worth.
  3. Recompute the fingerprintThe page shows the source string in full, and a button re-hashes it in your browser. To owe us nothing at all, the same command runs in a terminal:
    printf %s '<source string shown on the page>' | sha256sum
    The result must match the fingerprint shown, and the transaction's input data on the Base explorer.
  4. Open the transaction on the explorerThe link is on the page. The transaction date is the date the proof existed, and it does not come from us.

🎯 See an example proof · TDS-9222-TCEA

This example is a test proof issued on our own demo account, never a user's data. It behaves exactly like a real one.

Earn your own proofs

They compute themselves on your trades: connect your broker and the bar moves. Nothing to declare, nothing to type in, and the free plan is enough.

See pricing