Veridise primary-source snapshot
Last reviewed: 2026-04-27 UTC
Project status snapshot
- Official site: https://veridise.com/
- ZK audits page: https://veridise.com/audits/zk/
- Security tools page: https://veridise.com/security/tools/
- GitHub org: https://github.com/Veridise
- AuditHub client README: https://raw.githubusercontent.com/Veridise/AuditHub-Client/main/README.md
What the official materials say
1) Homepage and company framing
- URL: https://veridise.com/
- Key takeaways:
- Veridise frames itself as a blockchain-security company rooted in formal methods and smart-contract audits
- The homepage highlights 150+ completed audits and a 35+ person team, with explicit emphasis on academic / formal-methods background
- The current public positioning is broader than “audit firm” alone because the homepage repeatedly stresses internal tooling and ZK specialization
2) Zero-knowledge specialization
- URL: https://veridise.com/audits/zk/
- Key takeaways:
- Veridise presents ZK audits as a first-class product, covering circuits and dapps across Circom, Halo2, Nova, Plonky2, gnark, and related frameworks
- The page names customers and engagements including RISC Zero, Linea, o1Labs, Succinct, and Semaphore
- This is the strongest categorization clue for placing Veridise not just under generic smart-contract audits, but specifically under ZK security and formal-verification-heavy security infrastructure
3) In-house tooling surface
- URL: https://veridise.com/security/tools/
- Key takeaways:
- Veridise publicly documents internal tools including Vanguard, OrCa, ZK Vanguard, and Picus
- The tools span smart-contract static analysis, specification-guided fuzzing, ZK static analysis, and circuit determinism / underconstraint checking
- The page also references the
[V]specification language and LLZK, which further supports cataloging Veridise as a tool-building security organization rather than a pure consulting shop
4) GitHub organization signals
- URL: https://github.com/Veridise
- Key takeaways:
- The verified GitHub org ties Veridise directly to public code and research repositories
- The org surface includes ZK and security-focused repos such as Picus as well as AuditHub-related repositories and workshop materials
- This repo footprint matters because it demonstrates real public tooling and research artifacts beyond the marketing site
5) AuditHub programmatic workflow
- URL: https://raw.githubusercontent.com/Veridise/AuditHub-Client/main/README.md
- Key takeaways:
- The AuditHub client README documents a real API / CLI interface for Veridise’s analysis platform, including authenticated access, version uploads, task creation, monitoring, and log retrieval
- Command examples like
start-defi-vanguard-task,start-picus-v2-task, andmonitor-taskshow Veridise exposing tooling workflows that look more like a security control plane than a one-off consulting deliverable - This is especially relevant for the library because it shows Veridise shipping operational security infrastructure in addition to audits
Whitepaper / technical-doc status
- No single canonical Veridise company whitepaper or litepaper surfaced in this pass.
- The strongest current source of truth is the combination of the official marketing / capability pages and the GitHub / AuditHub client materials.
- For this project, the tooling and workflow docs are more informative than looking for a classic protocol paper.
Research notes
- Best current category for the library: smart-contract and zero-knowledge security / formal-methods audit firm / blockchain-security tooling.
- The main categorization clue is the combination of public ZK-specialist positioning and a concrete programmatic analysis surface through AuditHub.
- Veridise is a good example of a crypto security firm that is better understood as security infrastructure plus services, not just as a traditional auditor.