TL;DR: Scallop's monitoring gap came from a mismatch between Sui runtime semantics and EVM-first tools, Blockaid found, not just from alert volume. That kind of mismatch leaves privilege checks and containment logic exposed when the chain moves faster than manual response.
Editorial analysis by NHI Mgmt Group, based on content published by Blockaid: “How Scallop Secures its Lending Protocol with Blockaid's Onchain Monitoring”.
By the numbers:
- Scallop manages pools across 23 assets with approximately $130M in TVL.
- Scallop would have $130M+ uninsured against any attack without automated security monitoring.
- Since Q1-2026 implementation, Scallop has achieved MTTD under 1 minute from any anomalous onchain event.
Key questions
Q: Why do protocol teams need separate controls for financial and administrative risk?
A: Because the two risk classes behave differently and require different response paths.
Q: What signs show that manual incident response is too slow for onchain threats?
A: The clearest sign is that loss can occur before a human can triage, approve, and execute containment.
Q: What breaks when security monitoring is built on the wrong chain model?
A: Monitoring breaks when the control logic assumes a different execution model than the one the protocol actually uses.
Practitioner guidance
- Define chain-native detection logic Map monitoring to the protocol's native execution model, including object ownership, dynamic fields, and transaction semantics, instead of relying on EVM-style abstractions.
- Split economic and administrative alerts Create distinct monitors for oracle manipulation, liquidity and outflow anomalies, privileged function calls, and registry changes so response paths stay specific.
- Pre-authorise automated containment Use a programmable response that can pause the protocol or otherwise contain a confirmed threat without waiting for a manual approval chain.
Bottom line: Scallop's monitoring problem was not just alert volume, but a mismatch between Sui's runtime semantics and the assumptions built into EVM-first tools.
Glossary terms: Protocol-native monitoring, Caller authorization, Automated containment, Reward distributor logic
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Protocol-native governance is the new baseline for onchain monitoring: A detector that cannot reason about the chain's actual execution semantics is not a security control, it is a translation layer with blind spots. Scallop's Sui object model, dynamic fields, and Programmable Transaction Blocks required control logic that understood the runtime, not just the asset class. The implication is that governance programmes must evaluate monitoring by fidelity to execution, not by dashboard coverage.
A question worth separating out:
Q: Should teams prioritise detection fidelity or automated response first?
A: Detection fidelity comes first, but only if it is paired with a response path that can act on high-confidence events without delay. A precise alert that cannot trigger containment still leaves the protocol exposed. Teams should sequence the work so the most dangerous scenarios have both accurate detection and pre-authorised response, rather than treating alerting and containment as separate projects.
👉 Read our full editorial: Scallop's Sui monitoring shows why protocol-native detection matters