Protocol design & review
New constructions and existing ones: threat model, security argument, and the gap between the paper and the code that ships. Written up so your engineers and your auditors read the same document.
Cryptographer · Information security, and Privacy consultant
Proofs that hold
under adversaries.
Protocol design, cryptographic review and security architecture — from lattice assumptions and commitment schemes to key management that survives an audit.
CVE FEED
Loading the latest advisories…
Service status
- Loading…
Verdicts come from each provider's own status page. Crowd reports: downdetector.mx
IACR ePrint · newest
- Loading…
What I actually secure
six properties, not three- 01
Confidentiality
Who can read it
- 02
Integrity
Whether it changed
- 03
Availability
Whether it answers
- 04
Authentication
Who is speaking
- 05
Bit commitment
Bound before reveal
- 06
Privacy
What leaks anyway
How I work with clients
Implementation audit
Key management, randomness, side channels, and the parts of a library nobody reads. Findings ranked by what an adversary would actually do first, not by scanner severity.
Privacy engineering
Data minimisation, de-identification that survives linkage, and honest answers about what a system still leaks after the encryption is correct.