EIP-7702 Delegates: Nine of Ten Without Metadata Hashes Publish Source
A review of 59 contracts used as EIP-7702 delegates on Ethereum found that ten omitted the metadata hash normally appended to Solidity bytecode. Nine of those ten contracts nevertheless have verified source code on Blockscout; among the 46 contracts retaining a full metadata hash, 21 are verified there.
The sample covered 1,178 authorizations from a 200-block Ethereum window on 8 September. Of the authorizations directed to delegates without a metadata hash, 369 out of 371 pointed to contracts with published source. By comparison, 324 of 774 authorizations to full-hash contracts did so.
The stripped contracts include projects such as Uniswap’s CaliburEntry and Alchemy’s SemiModularAccount7702. The analysis suggests that removing the hash may help keep bytecode stable when metadata changes, but the projects did not state their reasons. The finding concerns code verification and contract transparency, not a change to Ethereum’s market fundamentals. Its scope is limited to one block sample and two verification services.
Neutral
This report is primarily about EIP-7702 delegate contract metadata and source verification, rather than token demand, protocol revenue, or a change to Ethereum’s security or monetary policy. It therefore provides no clear directional signal for ETH or the wider crypto market. The sample is also narrow: it covers one 200-block window, and the verification checks used only Blockscout and Sourcify.
In the short term, traders may pay attention to the results as a transparency and due-diligence issue. The contrast between the high share of authorizations going to source-published stripped contracts and the lower share for full-hash contracts could prompt closer scrutiny of specific delegates. However, the article does not report an exploit, loss of funds, or service disruption, so a broad market reaction appears unlikely. Any response would more plausibly be limited to users or projects interacting with the contracts discussed.
Over the longer term, the findings may inform debates about bytecode reproducibility, contract verification, and how metadata settings affect deterministic deployments. Similar transparency-related reports have tended to matter most when paired with evidence of a vulnerability, misrepresented code, or financial losses; none is established here. Traders should distinguish a missing metadata hash from proof that source code is concealed: nine of the ten stripped contracts were verified on Blockscout, and all eight queried on Sourcify received a match status, although not an exact match. Overall, the article is useful for contract-level risk assessment but does not by itself imply a bullish or bearish market catalyst.