How the check works.
Every product version is certified before it is listed, in six steps, and a person at Viroan makes the final decision. We sell software licences. We do not execute trades, manage accounts or hold client funds, and we are not authorised or supervised by KNF, ESMA or any other competent authority.
It reads the build. Not the pitch.
A marketplace can check two things about a trading product: what its author says about it, or what it does. Screenshots, equity curves and a description are the first. Everything below is the second. Four properties hold for every product in the catalogue — there is no premium tier of scrutiny, and no way to buy a softer one.
The source goes in, not a screenshot.
The creator submits the build and a declaration of what it is meant to do — which markets, which timeframes, which venues. The check reads both and looks for the gap between them. A product that quietly reaches the network, writes to disk, or trades an instrument it never declared is found here, and none of that is visible in a performance chart.
It runs on data the creator did not pick.
Periods, instruments and conditions are chosen on our side, after submission. This is the whole point: a strategy tuned until it looks good on a window its author selected will look ordinary on one he did not. Anything that only works on the author’s chosen window stops being interesting the moment the window moves.
A person puts their name on the verdict.
The analysis is automated and fast. The decision is not. Every run ends with a report on a human desk, and that person can stop a listing the machine was perfectly happy with — an unusual pattern, a declaration that reads wrong, something that fits no rule we have written yet. Suspicious flags found mid-run reach the same desk without waiting for the end.
It produces a record, not a rating.
The output is a document stating what was examined, under what conditions, and what came back — including what was not examined. It is not a score, not a recommendation, and not a forecast. A certificate tells you what happened on a bench. It does not tell you what will happen on your account.
Six steps. One standard.
Every certified product went through all six. A product that fails is returned with a written reason and can be resubmitted; it is not quietly ranked lower. There is no fast lane, and paying for placement does not move anything here — placement decides where a listing appears, never whether it passed.
Formal check.
The submission, the creator’s identity and the product’s declaration are checked first. Everything after this is measured against what was declared.
Static scan.
The source code is scanned against the declaration before anything runs.
Backtest.
The build is backtested on market data we hold, not on a period the creator picked.
Robustness and Monte-Carlo.
A battery of robustness and Monte-Carlo tests shows how the result holds up when conditions change.
Scoring against the declaration.
The results are scored against the limits the creator declared about their own product.
A person decides.
A person at Viroan makes the final decision. The verification engine scores and flags; it does not list or reject anything by itself.
What the document actually says.
A certificate on Viroan is five statements and their limits. Every one of them is about a specific build on a specific bench on a specific date. None of them is about the future, and the document says so in its own words rather than in a footnote.
Which build.
A hash of the exact artefact that went through the check. If what you downloaded does not hash to this, you are not holding the thing that was examined.
What was declared.
The creator’s own statement of scope, reproduced verbatim. Every later claim is measured against this text, including claims made in the listing.
What was run.
The periods, instruments and conditions used, chosen on our side. Enough detail that a reader can judge whether the bench was a fair one.
What came back.
The results, including the stress runs where it did badly. A certificate that only carries the flattering half of the evidence is an advertisement.
What was not checked.
The gaps, named. Conditions we did not simulate, venues we did not test, behaviour we could not observe on a bench. This section is never empty.
The catalogue is open. Pick a side.
Nothing here is a forecast, and nothing here is advice.
I want to read the evidence before I pay.
Every certified listing carries a certificate stating what was examined and what was not. You buy a licence to software that runs on your machine, against your own venue credentials, which Viroan never asks for.
What a buyer gets →I have a build and I want it read properly.
Submit it, and the six steps run against data you did not choose. You set the price and keep 85% of it. A rejection comes with the written reason and you can fix it and come back.
What a creator gets →One thing about the numbers.
The 85 / 115 split on the creator page is what we charge today and what we intend to go on charging. It is not a promise that it is permanent. Running the check costs money, and if the arithmetic stops working the numbers move — we would rather change a price in the open than quietly cut what the check actually does.
What we will hold to is the manner of it: not moving often, staying near where we started, and saying so before rather than after. What we will not do is invent a special older rate for people who arrived earlier. Everyone is on the same terms on the same day, and when the terms change they change for all of us at once.