Safe Edges is an Indian blockchain security firm. India is where the company was founded and where most of our team sits, so Indian clients get on-shore engagement management, IST working hours, direct access to the auditors doing the work, and contracting in a jurisdiction their legal team already understands.
India has one of the largest Web3 developer populations in the world and a domestic security supply that has not kept pace with it. Indian teams have historically paid international rates in USD for engagements run entirely across a nine-hour time difference, with the auditors and the engineers rarely in the same working day. That gap — not a shortage of technical talent in India — is the reason we exist.
Our Indian client base is broader than DeFi. It includes exchanges and brokerages, payments and fintech companies adding wallet or settlement functionality, enterprises running permissioned ledgers for supply chain and trade finance, gaming studios shipping on-chain assets, and IT services firms delivering blockchain projects for overseas clients who require an independent security review before acceptance.
For Indian teams selling into the US, EU, Japan or the Gulf, the audit report has a second job beyond risk reduction: it is a credential in someone else's procurement process. We write reports that hold up in that setting — documented methodology, rated findings, verified remediation — because a report that only satisfies your own team will stall in a foreign counterparty's security review.
Regulatory references describe the general shape of a regime and are not legal advice. Requirements change; confirm your obligations with your own counsel and supervisor.
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.
Yes. Safe Edges is headquartered in India with the majority of the audit team based here, and we work with Indian and international clients from that base.
Yes — custody architecture, withdrawal authorisation, deposit crediting, listing risk and platform penetration testing, plus the record-keeping and detection systems that regulatory obligations depend on.
Yes. Indian clients can contract domestically with GST invoicing and settle in INR; international clients contract in USD. Tell us which your finance team needs.
It is accepted on the quality of the work, not the postcode. Our reports carry documented scope, methodology, rated findings, proofs of concept and verified remediation, which is what a serious foreign counterparty or investor actually checks.
Yes — Hyperledger Fabric, Corda and permissioned EVM deployments, including the integration layer to enterprise systems, which is usually where the real risk sits.
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.