Before your audit begins, we want to ensure you fully understand the scope, importance, and value of an OpSec & Multi-Sig security review. This document covers what these audits examine, why they are critical to your protocol’s survival, and what recent real-world hacks have taught us.
<aside> 📌
⚠️ In 2026 alone, three major protocols lost over $600 million — not because their smart contracts had bugs, but because their operational infrastructure was left unguarded.
</aside>
The DeFi ecosystem has matured dramatically. Smart contract audits are now industry standard — which means attackers have adapted. They no longer just look for bugs in your Solidity code. They look for the humans, keys, and infrastructure surrounding your protocol.
<aside> 📌
<aside> 📌
| Metric | Value | Context |
|---|---|---|
| Total stolen via OpSec failures | $600M+ | Q1–Q2 2026 alone |
| DeFi hacks from key/access failures | 43% | Of all 2025 DeFi incidents |
| Smart contract audits Resolv had | 18 audits | Still lost $25M to an OpSec failure |
The third stat is the most alarming. Resolv Protocol had undergone 18 smart contract audits. None of them reviewed the off-chain signing infrastructure that was ultimately compromised. This is the gap that an OpSec audit fills.
An Operational Security Audit evaluates everything outside your smart contract code — the people, processes, tooling, and infrastructure your protocol depends on to operate securely.
A smart contract may be flawless, but if a privileged admin key lives in a shared AWS environment without access controls, your protocol is critically exposed.
| Domain | What We Review |
|---|---|
| 🔑 Key Management | Private key storage locations, HSM usage, AWS KMS configuration, key rotation policies, access logging. Single EOA vs. threshold-signature control. |
| ☁️ Cloud Infrastructure | IAM roles and permissions, secret management vaults, least-privilege enforcement, environment isolation (dev / staging / prod separation). |
| 👤 Access Control | Who can call admin functions? Are role grants time-locked? Are there emergency roles with unchecked power? MFA on all privileged accounts. |
| 🔗 Off-chain Components | Backend services that trigger on-chain operations, oracle price feeds, relayer nodes, keeper bots — evaluated for realistic compromise scenarios. |
| 🚨 Incident Response | Does the team have a monitored alert system? Is there a documented IR playbook? Can the protocol be paused within minutes of anomaly detection? |
| 👥 Social Engineering | Team communication channel security, device security policies, phishing resistance, insider threat modeling, and signer vetting procedures. |
| 📋 Governance Hygiene | Timelock durations on upgrades, quorum requirements, proposal vetting process, guardian and council key management. |
A Multi-Signature Wallet requires M-of-N keyholders to jointly authorize a transaction. This eliminates single points of failure. However, a poorly configured multi-sig can be worse than no multi-sig at all — it creates a false sense of security.
<aside> ✅
Properly Configured Multi-Sig
<aside> ❌
Common Multi-Sig Failures