Ethereum smart contract audits
HYDN audits Solidity contracts deployed to Ethereum mainnet. Mainnet holds the most value and attracts the most capable attackers, so beyond the standard review we pay particular attention to MEV and front-running exposure, gas behaviour, and assumptions broken by recent upgrades, such as transient storage locks and EIP-7702 delegated accounts.
What is specific to mainnet
- MEV and front-running. Mainnet transactions sit in a public mempool and are ordered by block builders. Any function whose outcome depends on ordering or on a price at execution time can be sandwiched or front-run. See front-running and MEV.
- Gas costs. Loops over unbounded arrays and expensive storage patterns can make functions too costly to call, or block withdrawals entirely.
- Transient storage. Reentrancy locks built on transient storage (EIP-1153, live since the Dencun upgrade) behave differently from storage locks, and need checking for how they reset within a transaction.
- EIP-7702. Since the Pectra upgrade, externally owned accounts can delegate to contract code. Contracts that treat “no code” as “not a contract” need revisiting.
- Composability. Mainnet protocols integrate deeply with each other. A change in one protocol’s behaviour, or a manipulated pool, becomes your problem.
What the audit includes
The full HYDN audit process applies: scope agreed against a commit hash, a manual review led by senior auditors, a private report with remediation guidance, up to two rounds of fix review, and a final report and certification you can publish.
Frequently asked questions
Does Pectra change how contracts should be audited?
Yes. Since EIP-7702, an address with no deployed code can still execute delegated contract code. Checks such as msg.sender == tx.origin or extcodesize == 0 no longer prove a caller is a plain wallet.
Do you audit on L2s as well?
Yes. We audit Solidity across all EVM compatible chains, including Arbitrum, Base, BNB Chain and Polygon.
Published Updated