Institutional Investors — Institutional blockchain security due diligence is an independent technical assessment of a protocol, platform or counterparty commissioned by an investor rather than by the team being reviewed — assessing exploitability, key and governance risk, engineering maturity and counterparty exposure, and returning a risk position an investment committee can act on.
When the investor commissions the review, the incentives change and so does the output. A team's own audit is scoped by the team; it tells you what they chose to have examined. An investor-commissioned review is scoped by your thesis and your exposure: how could this position go to zero, how quickly, and what would we see first. Those are different questions and they produce different documents.
We look at four things. Exploitability: what an attacker can take today, from the deployed code and the live configuration rather than from the repository at the commit that was audited. Authority: who can change the system, how fast, with what keys, and whether an upgrade or a treasury key defeats every other protection. Maturity: whether this engineering team can operate a live system safely, judged from their history, their process and how they handled past incidents. Counterparty: what they depend on that neither of you controls.
The output is written for an investment committee — a clear risk position, a small number of rated findings with plain-language impact, explicit unknowns, and a short list of conditions or monitoring that would make the position more defensible. Where we cannot get to a confident answer within the diligence window, we say so specifically rather than padding the memo.
We fix a commit hash, agree the in-scope contracts and read your architecture docs, then build a threat model: who the actors are, what the trust boundaries are, and which invariants must never break. Nothing is reviewed against assumptions we have not written down.
Line-by-line review by at least two auditors working independently, focused on authorisation, accounting, upgrade paths, external integrations and the gap between what the code does and what the documentation claims it does. Most critical findings come from this phase, not from tooling.
Static analysers appropriate to the language, plus property-based fuzzing and invariant testing to push the system into states no unit test covers. Tooling is used to widen coverage, never to replace the manual pass.
Candidate findings are proven on a forked network with a working proof of concept. We report what an attacker can actually do and what it costs them, not a theoretical severity label.
Every finding gets a severity rating, reproduction steps, the affected code, the impact in concrete terms and a specific remediation. You get a draft for discussion before anything is finalised.
We re-test every remediation against the original proof of concept and check that the fix has not opened a new path. The final report is yours to publish.
Because their audit was scoped by them, on a commit that may no longer be live, and it tells you nothing about upgrade authority, key custody, deployed configuration or how the team behaves in an incident. Those are usually where the position risk actually is.
A focused review typically runs three to ten business days depending on system complexity and whether the team cooperates. Tell us your committee date and we will tell you honestly what is achievable by it.
Yes, within limits. Deployed code, on-chain configuration, authority structure, history and public artefacts are all reviewable from outside. Private repositories and internal process are not, and we will state that boundary explicitly in the memo.
All three, plus counterparty onboarding. The framing changes: an equity position weighs team maturity more heavily, a token position weighs exploitability and authority, and an integration weighs what your systems inherit.
We say so, name the specific unknown, and tell you what access would resolve it. A memo that manufactures confidence it does not have is worse than no memo.
A repository or contract address, a commit hash to freeze the scope, whatever architecture or spec documentation exists, and a point of contact who can answer design questions. If documentation is thin we will write our understanding of the system back to you and ask you to confirm it — that step alone catches design-level bugs.
A single token contract is 24–48 hours. A typical dApp or mid-sized protocol runs one to two weeks. Large DeFi systems, L2s, bridges and ZK circuits are scoped per project after we have seen the code. We will give you a fixed timeline with the quote, not an estimate that moves.
Send the repository and a commit hash through the contact form, message @bugtester25 on Telegram, or book a 30-minute scoping call. 200+ protocols audited · $4B+ secured · 0 hacks post-audit. Prefer email? info@safeedges.in.