Blog

How TheDAO Security Grant Improved Dedaub's Bytecode Decompiler

If you’ve decompiled bytecode on app.dedaub.com, you may have noticed two improvements this year: more accurate, …

Smart Contract Monitoring: What Ours Actually Does

Smart contract monitoring used to be the thing teams bolted on after the audit, if they got round to it at all. That has changed. In our experience, more protocols are running monitoring as a standing function with a budget and an owner, the way an infrastructure team runs alerting. So it is worth being precise about what a monitoring product actually gives you, and about the fact that there are now two ways to get one running. Given access to a good-quality onchain dataset, you can choose to hire a security team to build for you, or build it yourself with an AI assistant doing the SQL.

How Smart Contracts Are Audited: The Methodology

Search “how are smart contracts audited,” and most of what you find is either a marketing checklist or a post-mortem of the latest hack. What is genuinely rare is a practitioner-grade account of how the work is actually done: what a senior auditor looks at first, how automated tooling and manual reasoning divide the labor, and what a rigorous review actually does with the source a project hands over. This article walks through that methodology as Dedaub practices it.

You Pay For What You Touch: Locality as Ethereum's Next Cost Model

This post is based on a talk given by Neville Grech at the Stateless Summit 2026, drawing on a 2021 study Dedaub conducted for the Ethereum Foundation on the impact of Vitalik Buterin’s Verkle tree gas metering proposal — the direct precursor of EIP-7864. TL;DR Real-world Ethereum contracts are written to fight today’s gas model — not to respect locality. Under EIP-7864, the unified binary tree replacing the 16-way Merkle-Patricia trie, access locality becomes a first-class cost dimension: you pay extra every time execution touches a code chunk or a storage slot that lives outside the small co-located region around the contract account. In a 2021 Dedaub study commissioned by the Ethereum Foundation, we measured a net ~26% gas cost increase on existing contracts under the precursor Verkle proposal, with ~96% of internal transactions worse off. That number sounds alarming. It is also a one-time, upper-bound repricing of contracts written with zero awareness of locality. Most of the gap is closable by compilers, standard libraries, and a handful of opt-in primitives. This post walks through the cost model, the systematic patterns that misbehave under it, and concrete optimization opportunities.

How TheDAO Security Grant Improved Dedaub's Bytecode Decompiler

If you’ve decompiled bytecode on app.dedaub.com, you may have noticed two improvements this year: more accurate, …

Smart Contract Monitoring: What Ours Actually Does

Smart contract monitoring used to be the thing teams bolted on after the audit, if they got round to it at all. That has …

How Smart Contracts Are Audited: The Methodology

Search “how are smart contracts audited,” and most of what you find is either a marketing checklist or a …