Cryptography and protocol engineering.
Zero-knowledge proof systems, signature schemes, consensus and execution layers in Rust. We make provers and verifiers faster, ship protocol changes and get code ready for audit.
- Engagements
- Monthly or a fixed review
- Review before audit
- Fixed price
- Language
- Rust, plus Solidity and TypeScript
- Code
- Yours, in your repositories
Protocol teams and companies building on cryptography.
You need a verifier made faster, a circuit proven, a signature scheme chosen or a consensus change shipped, and the people who can do it are hard to hire.
Zero-knowledge proofs
PLONK circuits and provers, KZG commitments, batch verification, MSM and FFT performance, verifier cost.
Signatures and curves
BLS12-381 signatures and aggregation, JubJub, Poseidon hashing, and safe handling of keys and subgroup checks.
Consensus and protocol design
Validator protocols, staking, fee markets and gas design, with the failure cases written down before the code.
Execution layers
WASM virtual machines and EVM execution, including host functions, metering and state management.
Review before audit
An engineering review of your cryptography so your audit finds less and costs less.
Post-quantum planning
An inventory of where your system depends on discrete-log assumptions and a migration plan you can act on.
Open source you can read.
Read the code before you talk to us. Every repository below is public.
We maintain an open-source PLONK implementation in Rust and lead the cryptography, consensus and VM work of a layer-1 blockchain, including an OP Stack-based EVM execution layer. We also built dario, a game that generates Groth16 proofs in the browser and verifies scores on-chain.
- Proof systemdusk-network/plonk ↗ PLONK with KZG commitments
- Curvesdusk-network/bls12_381 ↗ and jubjub ↗
- Hashingdusk-network/Poseidon252 ↗
- Executiondusk-network/piecrust ↗ WASM VM
- Nodedusk-network/rusk ↗
- Groth16 in the browserHDauven/dario ↗
Hein founded Mochavi and leads every engagement. He is your contact from the first call to delivery; Mochavi's senior engineers do the work with him.
Monthly or fixed.
A technical call
Thirty minutes with Hein on your code and the bottleneck. No sales call first.
Monthly or fixed review
Senior engineering by the month for performance and protocol work, or a fixed-price review before audit.
Measured results
Benchmarks before and after on your hardware, pull requests to your repository, written notes on every decision.
Questions buyers ask.
Can Mochavi make our PLONK prover or verifier faster?
Yes. We maintain an open-source PLONK implementation in Rust and work on MSM and FFT performance, batch verification and verifier cost. We benchmark before and after on your hardware and deliver the changes as pull requests to your repository.
Do you replace an audit?
No. We make your code ready for one and fix what the auditors find. An independent audit is still the right call for anything holding value.
Can you work on our existing codebase?
Yes. Most cryptography work is on existing code: making a verifier faster, fixing a soundness issue or adding a feature to a circuit.
Who would actually do the work?
Senior Mochavi engineers, led by Hein, who stays your contact throughout.
Who owns the code?
You do. Open-source contributions stay under your project's license.
Tell us what has to work.
Describe the system and the deadline. We reach out within five days; the first call is free and confidential.
Or email hello@mochavi.com

