Join our Newsletter — 33% off our NHI Course

Why do onchain losses happen so fast in Web3 security?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: Onchain security fails when teams rely on post-transaction detection for threats that complete in seconds, according to Blockaid. Transaction controls have to move before signing if value can settle faster than human review.

Editorial analysis by NHI Mgmt Group, based on content published by Blockaid: “Blockaid's View on Security”.

Key questions

Q: Why do public blockchain networks increase security risk even when the code is open and auditable?

A: Public visibility gives attackers free reconnaissance.

Q: What are the signs that onchain risk is being managed as separate cyber, fraud, and compliance problems?

A: The main sign is fragmented ownership.

Q: How should teams prevent onchain losses when transactions settle too fast for manual review?

A: Teams should move controls to the point of action.

Practitioner guidance

  • Map transaction approval points Identify every place where a user, signer, or automated workflow can authorize value movement, then classify which of those points still rely on post-event review.
  • Simulate and score transactions before signing Use pre-execution analysis to inspect approvals, contract interactions, and fund flows so suspicious outcomes can be blocked before broadcast.
  • Unify fraud, compliance, and cyber review Create one operating view for exploit patterns, sanctions exposure, and behavioural fraud so teams do not hand off the same event across separate queues.

Bottom line: Onchain security fails when teams rely on post-transaction detection for threats that complete in seconds.

Glossary terms: On-Chain Security, Transaction Simulation, Multisig and MPC Operations, Real-Time Risk Prevention

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Onchain security is really identity governance under extreme time pressure: the control problem is no longer just asset protection, but deciding what principals can act, sign, or delegate before value leaves the system. When the principal is a wallet, a smart contract, or a multisig signer, the governance model has to account for machine-speed execution and public observability. That makes service account security a useful analogue, because both domains depend on scoped authority, lifecycle control, and revocation discipline. Practitioners should treat onchain permissions as governed identities, not just cryptographic objects.

A question worth separating out:

Q: How do security, fraud, and compliance teams share accountability for onchain transactions?

A: They need a common control objective: stop unsafe value movement before it happens. Security owns technical enforcement, fraud owns behavioural and social indicators, and compliance owns illicit flow and sanctions exposure, but the programme fails if those responsibilities are not joined at the transaction layer.

👉 Read our full editorial: Onchain security demands real-time control as value moves faster


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.