Dedaub

• Name: Dedaub
• URL: https://dedaub.com/
• Category: smart-contract security company / onchain security-intelligence infrastructure operator / decompiler and transaction-analysis control plane
• Tags: ethereum-ecosystem
• Summary: Dedaub belongs in companies/, not only projects/, because the practical authority is not just in one decompiler page or one audit PDF. The useful question is which named organization maintains the decompilation pipeline, detector logic, monitoring products, token-risk verdict surfaces, audit archive, and downstream API access that wallets, exchanges, and protocols may start treating as security workflow truth. That authority sits with the Dedaub organization more clearly than with any isolated repo or branded product page.
• What it does:
  • Performs smart-contract audits, architectural reviews, risk-mitigation work, protocol-design advisory, and gas-optimization engagements for crypto teams
  • Operates a broader Security Suite spanning bytecode decompilation, vulnerability detection, and transaction analysis across EVM ecosystems
  • Publishes a public decompiler that reconstructs Solidity-like logic, storage layout, ABI, and intermediate representations directly from deployed bytecode, including for contracts without verified source
  • Ships downstream security products including Tok{In} for token-risk detection, Monitor for protocol-specific multichain monitoring, and Firewall for pre-execution transaction protection
  • Maintains a public GitHub surface and audit archive that turn company-authored review work and tooling into reusable infrastructure for downstream teams
• Key claims:
  • The homepage says Dedaub combines experienced auditors with blockchain transaction monitoring, smart-contract analysis technologies, and decompilation of contracts even without source or ABI, which is analytically useful because it frames the company as operating security infrastructure rather than only selling point-in-time reviews
  • The homepage also frames the Security Suite as a unified indexed multichain intelligence layer with millions of contracts decompiled, millions of threats detected, and tens of billions of transactions analyzed, showing that the practical surface is ongoing company-run data and analysis workflow rather than one static code artifact
  • The decompiler product page says the system reconstructs functions, control flow, storage layout, state transitions, ABI, TAC, Yul-style output, and disassembly from deployed EVM bytecode, and that it is free for individuals while offering API access for organizations; that API-access boundary is exactly the kind of operator layer that belongs under a named entity note
  • The official product pages explicitly say Dedaub’s downstream applications include token-risk detection for wallets, exchanges, and AI trading agents, protocol-specific monitoring, and transaction-level protection, which means Dedaub can sit upstream of other operators’ block/allow decisions
  • The public Dedaub/audits repository acts as a company-authored security-report corpus spanning clients such as AORI, Blur, Chainlink, DeFi Saver, Ethereum Foundation, GMX, Immunefi, Lido, Liquity, and Yearn, reinforcing that Dedaub shapes public review norms in addition to shipping tooling
  • Taken together, the current primary-source surface says the real control surface is the company boundary around decompilation coverage, detector design, monitoring policy, API access, and risk scoring, not merely an audit shop label
• Whitepaper: No classic Dedaub company whitepaper is the point here. The strongest primary materials are the official site, decompiler and monitoring product pages, public GitHub organization, and audit archive, plus the broader source capture in ../whitepapers/dedaub-primary-sources-2026-04-30.md.
• Sources:
  • https://dedaub.com/
  • https://dedaub.com/product/decompiler/
  • https://dedaub.com/web3-security-monitoring/
  • https://github.com/Dedaub
  • https://github.com/Dedaub/audits
  • https://api.github.com/orgs/Dedaub/repos?per_page=100
  • https://api.github.com/repos/Dedaub/audits
  • https://api.github.com/repos/Dedaub/audits/contents
  • ../whitepapers/dedaub-primary-sources-2026-04-30.md

Internal linkages

• Project-layer alias: dedaub.
• Strong adjacent company comparisons: openzeppelin, trail-of-bits, and blocksec.
• Useful project-surface contrast where formal methods matter more than an operator platform: certora.

Protocol / company boundary

• projects/dedaub is now only an alias because Dedaub is not most usefully analyzed as a standalone protocol or neutral primitive.
• The product surfaces still matter: decompilation, transaction analysis, monitoring, firewalling, and token-risk detection are real technical interfaces.
• But the cleaner analytical question is organizational: who decides coverage, detector logic, API access, monitoring defaults, and how Dedaub-authored security verdicts get packaged for downstream wallets, exchanges, and protocol operators?
• That is why this note belongs in companies/: the practical authority is in the organization operating and publishing the security-intelligence stack, not in an independent Dedaub protocol.

Control surface

• Practical leverage sits in bytecode coverage, detector design, decompiler output quality, monitoring configuration, token-risk heuristics, API admission, and where Dedaub’s transaction-risk or monitoring products get embedded downstream.

• Even where output is public, the company still shapes report framing, dataset freshness, customer workflow integration, documentation emphasis, and which security interpretations other operators start treating as authoritative.

• Read the durable choke point here as who gets to define and distribute the security verdict surface?, not only which audit report or tool page exists?

• Last reviewed: 2026-08-07 UTC