Blockchain Vulnerability Assessment — A blockchain vulnerability assessment is a breadth-first enumeration of the known and discoverable weaknesses across a blockchain estate — contracts, nodes, RPC endpoints, APIs, dependencies and key handling — verified by hand to remove false positives and returned as a severity-rated register you can work through in priority order.
Assessment is about coverage; penetration testing is about depth. A vulnerability assessment answers "what is wrong across everything we own?" rather than "how far can one attacker get?". Both matter, and running the assessment first almost always makes the penetration test cheaper and sharper, because the tester starts from a map instead of from zero.
The reason to pay a specialist rather than run a scanner is the verification pass. Automated tooling across contracts, hosts and dependencies produces a large volume of output with a low signal ratio: severities assigned without context, findings unreachable in your configuration, and — more dangerously — silence where the tool has no rule. Every finding we report has been reproduced by a human, rated against your actual deployment, and stripped of the ones that cannot fire.
This works well as a recurring engagement. Estates drift: a new node goes up, a dependency picks up a CVE, a contract is redeployed with different parameters, an endpoint that was internal becomes reachable. A quarterly assessment against a stable baseline turns that drift into a short delta report instead of an annual surprise.
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.
| Severity | What it means |
|---|---|
| Critical | Direct loss of funds or permanent freezing of assets, exploitable by any actor. |
| High | Loss of funds or protocol insolvency under realistic conditions, or requiring a privileged actor to misbehave. |
| Medium | Broken protocol behaviour, denial of service, or value leakage that does not directly drain the contract. |
| Low | Edge-case incorrectness with limited impact, or an issue requiring implausible preconditions. |
| Informational | Code quality, gas efficiency, documentation mismatch and defence-in-depth suggestions. |
Single token contract: starts from $999, report in 24–48 hours. dApp, GameFi or RWA project: starts from $2,999. DeFi protocol, L2 / rollup, Bridge, ZK circuit, AI agent / MCP: scoped per project after we have seen the code.
An assessment enumerates weaknesses broadly across everything in scope. A penetration test picks the promising ones and chains them to prove real impact. Assessment gives you coverage and a work queue; penetration testing gives you proof and priority.
Scanners are the starting point, not the deliverable. Their output is verified by hand, re-rated against your deployment, and cut down to findings that can actually fire. The value is in what we remove, and in what the tools never had a rule for.
Quarterly for an active estate, or after any material change: a new chain, a new node cluster, a redeployment, a migration or an acquisition. Recurring runs are much cheaper because they diff against a known baseline.
Yes. Integrations, forked code and inherited contracts are frequently the highest-risk part of an estate precisely because nobody in the current team owns them.
Days rather than weeks for most estates. Scope drives it — the number of live contracts, hosts and services, not the number of lines of code.
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.
Yes. Fix review is part of the engagement, not an upsell. We re-run the original proof of concept against your patched code and confirm the fix has not introduced a new path.
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.