Development
Systems, tooling, and research infrastructure I build for zero-knowledge and blockchain security.
I build security-relevant systems, tooling, and research infrastructure for the ZK and blockchain ecosystem.
This page complements the Audits page by showing the engineering side of my work: the systems I contribute to, the tools I build, and the kinds of internals I spend time understanding deeply.
Selected work
ZP1
Core contributor to the ZippelLabs zkVM. My work here centers on understanding zkVM architecture, execution assumptions, proof-system security boundaries, and the kinds of implementation details that matter during adversarial review.
Focus: zkVM internals, proving-system assumptions, system architecture
ZSentinel
A monitoring and alerting system for ZK proof infrastructure. Built to improve operational visibility around proving pipelines, system failures, and security-relevant anomalies in production-style environments.
Focus: monitoring, alerting, proof-system operations, security visibility
zk-risc-v-vm
An experimental RISC-V zkVM implementation used to explore execution models, proving flows, verifier-side design, and the engineering trade-offs behind virtual-machine-based proving systems.
Focus: RISC-V execution, zkVM experimentation, verifier design
my-bridge
Cross-chain bridge research and implementation focused on trust boundaries, message verification, and common failure modes in interoperability systems.
Focus: bridge security, cross-chain messaging, trust assumptions
Why this matters for audits
Building systems changes how you audit them. It forces you to reason about:
- architecture, not just isolated code paths
- operational assumptions, not just local correctness
- verifier and proving boundaries, not just happy-path logic
- trade-offs between performance, usability, and security
That engineering context directly informs how I approach reviews of zkVMs, L2 infrastructure, cryptographic systems, and high-value smart contract codebases.