Technical due diligence for crypto and AI.
An independent read on a company's technology, security and team before you invest or acquire, written by engineers who build the same kind of systems.
- For
- Investors and acquirers
- Deliverable
- Red-flag summary, full report, 100-day plan
- Interviews
- With the people who wrote the code
- Conflicts
- Checked before we accept
Investors and acquirers.
You need to know whether the technology does what the deck says, what it would cost to fix what it doesn't and who it depends on, before your investment committee meets.
Architecture and code
How the system is built and tested, and what will break first at ten times the load.
Cryptography and protocol risk
Whether the cryptography is sound, audited and correctly used, and what an exploit would cost.
AI dependence
Which models the product depends on, what that costs per customer and who owns the data.
Team and key people
Who can change the system safely today and what happens if one of them leaves.
Security posture
How keys, secrets and customer data are handled, and the last incident they had.
What the report contains.
A sample table of contents. Length depends on the target; the summary always fits on two pages.
We build regulated finance systems, zero-knowledge cryptography and AI agents. We know what good looks like because we ship it. Every report is signed off by our founder, Hein Dauven.
- Red flags and deal-relevant findings (2 pages, for the committee)
- What the product really does, compared with the deck
- Architecture, code quality and test coverage
- Cryptography, protocol and security review
- AI and third-party dependencies, cost per customer
- Team, key people and hiring risk
- 100-day plan with cost estimates
- Appendix: evidence, interviews, repository statistics
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.
Mochavi is paid by Dusk to provide its technology leadership. That is our strongest credential and a possible conflict, so here is how we handle it. We recommend Dusk only when its privacy and compliance features fit your case, and we say so when another chain fits better. In due diligence we disclose any Dusk connection up front and decline targets that compete with Dusk or depend on it.
From NDA to committee.
NDA and conflict check
Before any material is shared. We tell you straight away if we have to decline.
Evidence
Data room, code access and interviews with the people who wrote the code.
Report
Red-flag summary first, then the full report and a call with your deal team, timed to your committee date.
Questions buyers ask.
Can Mochavi assess a blockchain, zero-knowledge or AI company before we invest?
Yes. Our engineers build zero-knowledge cryptography, blockchain protocols and AI agents themselves. We review the target's architecture, code, cryptography, AI dependencies, security and key people, and deliver a two-page red-flag summary for your committee, a full report and a 100-day plan with cost estimates.
Is leading Dusk's technology a conflict?
It can be. We disclose the Dusk connection in the engagement letter and decline targets that compete with Dusk or depend on it. For everything else, the Dusk work is why we can judge the cryptography.
How do you handle confidentiality?
We sign your NDA before any material is shared, keep data in your data room where possible and delete copies after delivery.
Do you talk to the target's team?
Yes, with your agreement. Interviews with the people who wrote the code are the fastest way to the truth.
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