BlockSec

• Name: BlockSec
• URL: https://blocksec.com/
• Category: crypto security operations / transaction simulation / compliance and investigation tooling
• Summary: BlockSec is a security operations vendor, not just an audit shop. Its real product is an offchain control plane: simulation, monitoring, response, and compliance tooling wrapped around wallets, protocols, exchanges, Safe flows, and L2 sequencer operations.
• What it does:
  • Performs audits for smart contracts, wallets, and blockchain infrastructure, including L1/L2 systems
  • Runs Phalcon Security for monitoring, alerting, and in some cases automated threat blocking across protocol, treasury, exchange, and sequencer workflows
  • Sells compliance and investigation tooling through products such as Phalcon Compliance and MetaSleuth for screening, tracing, and case management
  • Exposes transaction simulation and explorer surfaces so partners can inspect likely state changes and balance impacts before execution
  • Publishes incident and research material through its incident library, research hub, and GitHub organization
• Key claims:
  • The company markets itself as a combined compliance-and-security platform rather than a single-product vendor
  • Official docs present a broad product map spanning audits, monitoring, simulation, compliance, Safe monitoring, L2 security, and anti-MEV / policy surfaces
  • Phalcon Security is positioned as a prevention stack that can detect operational and financial threats and sometimes trigger action before damage lands
  • The transaction-simulation API and Phalcon Explorer make the platform more operational than a pure audit or advisory firm
  • The public incident library and research output show that incident intelligence is part of the product surface, not just supporting marketing copy
• Whitepaper: No canonical standalone BlockSec whitepaper or litepaper surfaced in this pass. The clearest current sources of truth are the official site, docs, research hub, security-incident library, and GitHub organization; see ../whitepapers/blocksec-primary-sources-2026-04-28.md.
• Sources:
  • https://blocksec.com/
  • https://docs.blocksec.com/about-blocksec.md
  • https://docs.blocksec.com/phalcon/phalcon-security
  • https://docs.blocksec.com/transaction-insights/transaction-simulation-api
  • https://blocksec.com/research
  • https://blocksec.com/security-incident
  • https://github.com/blocksecteam

Internal linkages

• Best comparisons: hypernative, blockaid, and trm-labs.

Control surface

• The leverage is offchain: detection logic, simulation, policy thresholds, case workflows, and whether a customer lets BlockSec escalate from alerting into blocking or other response.

• The monitored assets stay on external chains. The consequential decisions sit in BlockSec-managed service layers and operator runbooks.

• Treat it as security/compliance middleware around onchain activity, not as an onchain primitive.

• Last reviewed: 2026-06-03 UTC