Cryptography · focus area
Privacy-preserving financial compliance
Privacy and compliance are usually framed as opposites. Most of my work sits exactly on that line: systems that keep data confidential while still letting regulators, auditors and counterparties verify what they need to. It's one of the hardest and most useful problems in the space.
The toolkit
View keys & selective disclosure
Letting the right parties see the right data — and no one else — without breaking a shielded system's privacy guarantees.
Threshold cryptography
Splitting trust across parties so that disclosure or decryption requires a quorum, not a single point of failure.
Trusted execution environments
Using TEEs such as Intel SGX to run sensitive logic with hardware-backed confidentiality, and understanding their real-world limits.
Auditability by design
Building systems where compliance checks are provable rather than bolted on, drawing on work like Transaction Controls in Zcash.
This is part of my cryptography practice. If you're designing a system that has to be both private and compliant, that's squarely in scope.