1 validator pair runs, and the validator reads the leader's result
agreement, 2 out of 2the contract uses gl.nondet.exec_prompt to reach consensus on the interpretation of multiple source documents
necessity, 2 out of 2text is sliced before the prompt, which changes its length but not its shape
untrusted, 1 out of 21 block is drawn, but no stored state is copied to memory first
boundary, 1 out of 234 raises, and a timeout or an empty answer is not addressed
failure, 1 out of 2Why two numbers
They are never averaged. A careful contract behind a site that calls a transaction done the moment it is sent is a different problem from a weak contract behind an honest site, and one number would hide it.
What the number is
A sum of five marks against anchors published before anything was scored, each one derived from the executable structure of the source or judged by validators who read it independently, so the number says where this file sits against a fixed standard rather than against whatever else was reviewed that week.
Before you deploy
Where the next point is
Each row is why a mark landed where it did and the anchor one step up, as the contract published it. Counted criteria come first, since changing the source is certain to move them.
text is sliced before the prompt, which changes its length but not its shape
next the characters that could close a block are neutralised at the prompt boundary
1 block is drawn, but no stored state is copied to memory first
next one block per decision, with stored data copied to memory before it
34 raises, and a timeout or an empty answer is not addressed
next every branch that can fail raises something a reader could act on
The rules check
Advisory and never scored. Each finding names a rule a real rejection or a failed deployment paid for, read off the code this contract can actually run.
No finding. None of the checks fired on the code this contract can run.
Deploy these exact bytes
The file is fetched again and has to hash to this report's digest before anything is signed, so what goes on chain is exactly what was reviewed. It deploys from your own wallet, and the new contract is yours.
Which network
A review is about bytes, not about a network, so the same reviewed file can go wherever you want it to run. Your wallet is asked to switch before anything is signed.
Charges nothing, and the network this review was run on.