Verified Quant Track Record: Data, Strategy and Evidence

A quant track record needs separate evidence for data origin, calculation method and the strategy that produced the trades. A broker connection or analytics badge addresses only part of that chain. It does not independently prove profitability, future performance, legal identity or that a particular algorithm generated every order.

State Exactly What Was Checked

Use terms such as broker-sourced, statement-imported, simulated, backtested or independently examined only for evidence that supports them. Do not turn a connection status into “irrefutable proof of an edge”. A historical profit is an observation about a particular record, not a forecast.

Preserve Account Type, Coverage and Selection

Distinguish a historical simulation, forward demo, a simulated prop evaluation and an account executing under its actual broker conditions. Read the provider's account context rather than inferring it from a public profile name. State the start/end dates, collection gaps, closed and open position coverage, currency and treatment of fees.

Record which accounts and strategy variants were included and which were excluded, with the reason. Selecting only successful accounts, restarting after losses or choosing parameters after seeing the reported period can bias a presentation. A direct connection to one chosen account does not show the results of unreported accounts.

Keep original statements and source files with retrieval dates. A file hash can detect a change against a retained reference copy; it does not prove who created the file or that the broker issued it. A screenshot can document a screen state, but does not supply the omitted underlying history. Neither manual nor automated records are automatically complete.

Link the Report to a Strategy Version

Identify the strategy code version, parameters, instrument universe and dates it was actually active. Preserve order/deal IDs and execution logs where available. Mark manual trades, risk overrides, restarts and changed parameters. A current source-code archive is not evidence that the same code ran throughout an older performance period.

Keep development, selection and later evaluation periods distinct. Disclose parameter searches and changes instead of calling a retrospectively selected result an untouched forward test. The number of trades alone does not establish statistical significance: dependence, strategy changes, costs, market conditions and the selection process matter. No universal minimum sample, pass rate or own-account study is asserted here.

Reconcile Money Before Comparing Ratios

For a hypothetical account with initial equity of 10,000, final equity of 12,000, deposits of 3,000 and no withdrawals or other external flows, net trading result is 12,000 − 10,000 − 3,000 = −1,000 in the account currency. The raw balance increase of 20% is not the trading return.

Cash-flow timing matters. If the 3,000 deposit was made at the start before the measured trading, 13,000 declining to 12,000 is about −7.69%. If it arrived only at the end, 10,000 declining to 9,000 before that deposit is −10%. A final balance alone cannot choose between those paths. Use a documented return method and the required valuations rather than inventing missing inputs.

For ratios, state whether the series uses trade results, calendar-day returns, represented trading days or another basis. Keep gross versus net costs, annualization, risk-free rate, standard-deviation convention and zero-denominator handling explicit. A closed-trade curve does not reconstruct every floating equity dip; low observed drawdown does not prove that a continuously enforced provider floor was never crossed.

Understand Investor Access and the MyVeridex Badge

MetaQuotes documents that MT5 investor authorization can inspect the account but cannot trade. That permission does not independently authenticate identity, make records immutable or guarantee that every historical event is returned. MyVeridex's native connection paths are MT4/MT5, subject to the actual account and server. It is not a universal investor-password connector for cTrader, DXtrade, Match-Trader or TradeLocker.

The current MyVeridex badge explanation describes a recorded product status. The scheduled evaluation checks an accepted collection method, a successful sync less than 24 hours old, a MyVeridex account record at least seven days old, at least ten recorded trades, no recorded manual balance-edit timestamp and active status.

Connection, reconnect and sync updates can also set Verified outside that scheduled evaluation. The badge alone therefore does not show that all six conditions were just checked. Seven days is the MyVeridex record's age, not proof of the broker account's age; ten trades is a product threshold, not evidence of a reliable strategy. Statement import alone does not meet the scheduled accepted-method condition. A separate optional ownership check is not an independent audit or legal identity verification.

Share a Reviewable Record With Its Limits

Provide the period, account context, source method, retrieval/sync date, cost and cash-flow basis, strategy version, included accounts and unresolved gaps alongside the report. Keep the disclosed scope consistent between a public profile, investor report and underlying records. Redact unnecessary personal or account access details before sharing.

MyVeridex can present available-record analytics and shareable reports. It does not promise an independent audit, a cryptographically immutable history, automatic investor acceptance or approval by any prop firm. The UTC closed-record Prop Tracker summary is not the provider's complete intraday equity and rule engine. The recipient defines what additional evidence it requires.

A 7-day free trial is available to assess the implemented data path and reports.