🌐 EN
ENESRUUK
Audit · public reports · independent eyes

The discipline of being
checked.

BivaraX2 is auditable from the day code is written. Independent firms inspect the cryptographic core, the dual-device protocol, and the server-side claims — and I publish their reports as they arrive, with their findings, with my remediations, without softening either.

A privacy claim that has not been audited is a press release. An audit that has not been published is a press release with extra steps.

— BivaraX2 · The Discipline of Verification

The audit register

Every audit. Every report.
In one place.

The list below is the complete record — past, current, and scheduled. I will not remove items, even if they are unfavourable. The audit trail is the trust trail.

2026 · Q4
Cryptographic core · pre-beta

Initial review of PQXDH & Double Ratchet implementation

First-pass audit by Trail of Bits. Scope: key exchange, ratchet, AEAD wrapping. Beta-blocking findings only.

Scheduled · Q4 2026 Report pending
2027 · Q1
Dual-device protocol

Cross-Guard handshake formal verification

Formal model of Cross-Guard signing flow, written in Tamarin. External cryptographers verify replay, forge, and rollback resistance.

Scheduled · Q1 2027 Report pending
2027 · Q2
Public beta · full scope

Independent full-stack audit

Cure53 reviews iOS, Android, and Desktop clients end-to-end. App, transport, key management, side channels, OS integration.

Scheduled · Q2 2027 Report pending
2027 · Q4
Open-source release · Phase XI

Reproducible build verification

Independent verification that the binaries on app stores match the open-source code, byte for byte. Performed by NLnet researchers.

Scheduled · Q4 2027 Report pending
2028 · annual
Continuous · ongoing

Annual full re-audit

From Phase XII onward, I commission an independent annual audit. Findings published the same week they are received.

Recurring Reports as released
How I hold ourselves accountable

Six rules of publication.

An audit programme is only useful if the publication discipline is stronger than the marketing department. Here are the six rules I have committed to publicly — and have agreed to bind ourselves to in writing.

Rule 01

Every audit gets published

Favourable, mixed, or unfavourable. An audit I commission is an audit I publish — in full, with the auditor's findings as written.

Rule 02

Findings stay visible

I do not delete reports after I patch the issues. The remediation is added below the original finding. The history is the receipt.

Rule 03

Auditors choose their words

Reports are published verbatim. I do not edit, summarise, or "translate for non-technical readers." My PR team does not see them before You do.

Rule 04

A bad audit pauses the roadmap

If an audit finds a critical flaw, I pause public phases and migrate. I do not ship the next phase to obscure the previous report. Bad news has the right of way.

Rule 05

No NDAs with auditors

Auditors are free to discuss their findings publicly, write blog posts, present at conferences. I do not buy silence.

Rule 06

Independence by contract

Auditing firms cannot also be paid for "remediation services" by me within 24 months of an audit. The auditor cannot benefit from finding nothing.

— Want to audit BivaraX2 yourself? —

The code is open. The audits are above.
The findings are welcome.

Independent researchers can request access to pre-release code via the bug bounty channel. Contact details on the bounty page.

See the Bug Bounty Contact security