VIRP.systemsTalk to an engineer
Hostile reviews, kept

Independent review sessions built it, ran it, and tried to break it. We publish what they found.

How to read this table

Most were AI-assisted reviews in fresh, isolated sessions. They are not reviews by a firm, and we say so.

DateReviewerWhat they didTop findingOutcome
2026-08-05ai-assistedBuilt and ran the C, Python, and Go suites; wrote four attack harnessesApprover signatures not in the chain.Fixed with the Ed25519 migration.
2026-08-15ai-assistedBuilt and ran the suite; independently confirmed two prior fixesRestart laundering.Fixed, confirmed by the reviewer.
2026-08-21ai-assistedArchitecture review: needed or just neat?Half of VIRP is unnecessary if you trust the operator.You should not have to.
2026-09-01ai-assistedRe-review of the current treeThree camera-path findings gating the “signed all the way through” claim.Open.

Full review record on the protocol site