Research notes.
How backtests go wrong, and what Evrant’s engine does about it. Each page answers one question in plain language, cites the primary research, and says which parts are built and which are not.
- Worked exampleA real verification case that needed workArchived synthetic engine verification: three walk-forward windows, a needs-work outcome and the receipts behind it.
- GuideBacktest validation and leakageWhy a strong backtest is weak evidence, the three ways leakage gets in, and how the engine refuses each one.Reviewed
- GuideOne-minute bars and their limitsWhat a bar records, why the order of prices inside it is unknown, and which strategies bar data cannot test honestly.Reviewed
- ReferenceCompatibility and ownershipC# on the Evrant SDK, MCP clients, what is not included, and what you own when you leave.Reviewed
Written by Evrant engineering. Product details are checked against the engine source and specification on the review date. Figures are illustrative unless a page says otherwise, and nothing here is a performance claim or investment advice. For the product itself, start with how it works or validation.
Early access
Be first to hear when it’s ready.
Join free for an early-access invitation. No account or payment required. We’ll confirm market coverage before you choose a plan.
You’re on the list. We’ll email you when your invitation is ready.
For your early-access invitation only. Request removal anytime at [email protected]. See our privacy notice.