<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>VEDa Investigations</title>
        <link>https://paragraph.com/@vedInvestigates.xyz</link>
        <description>undefined</description>
        <lastBuildDate>Tue, 25 Aug 2026 23:49:31 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Investigating Why Four Consecutive ETH Transfers Failed to the Same Address]]></title>
            <link>https://paragraph.com/@vedInvestigates.xyz/investigating-why-four-consecutive-eth-transfers-failed-to-the-same-address</link>
            <guid>9ShUgJiB9Qzii7nUWnnW</guid>
            <pubDate>Wed, 17 Jun 2026 10:28:13 GMT</pubDate>
            <description><![CDATA[Four consecutive ETH transfers failed despite using Ethereum's long-standing 21,000-gas transfer allocation. A fifth attempt succeeded only after additional gas was supplied.
What initially appeared to be a routine out-of-gas error turned into an investigation involving EIP-7702 delegation metadata, recipient-side execution traces, and a transfer that consumed 21,055 gas instead of the expected 21,000.
This report documents the evidence, findings, and limitations of that investigation.]]></description>
            <content:encoded><![CDATA[<div data-type="x402Embed"></div><p><strong>Executive Summary</strong></p><p>This investigation examined five ETH transfer attempts on Ethereum Mainnet between the same sender and recipient. Four attempts failed at the 21,000 gas ceiling, and a fifth attempt succeeded after the sender increased the gas limit to 33,003. The successful transfer consumed 21,055 gas. Etherscan surfaced MetaMask EIP-7702 delegation metadata associated with the recipient address across the observed transactions, and Tenderly traces indicated recipient-side execution during the failed attempts.</p><p>The available evidence supports the conclusion that the traditional 21,000 gas heuristic was insufficient under the conditions present for this recipient. The report does not establish the precise mechanism responsible for the additional 55 gas units, but the transaction pattern is consistent with recipient-side behavior associated with the delegation metadata.</p><p><strong>Transaction Parties</strong></p><p>Role	Address</p><p>Sender	0x80969F85331acFC7cA2f3b3586B54dE359583839</p><p>Recipient / Authority Address	0x215FA41D13E0D374d58A4554eFaE059d1Bd13B43</p><p>MetaMask EIP-7702 Delegator surfaced by Etherscan	0x63c0c19a282a1B52b07dD5a65b58948A07DAE32B</p><p><strong><u>Observed Transaction Pattern</u></strong></p><p>Five transfers were identified between the same sender and recipient:</p><p>Four consecutive attempts failed at exactly 21,000 gas.</p><p>A fifth attempt succeeded after the gas limit was increased to 33,003.</p><p>The successful transaction used 21,055 gas.</p><p>The successful transaction had nonce 4, confirming it was the fifth submission from the sender.</p><p><strong>Representative Failed Transaction</strong></p><p>Attribute	Value</p><p>Transaction Hash	0xcfbfdeb2e907af049805c5944b424febcf8d7ab343c41f7fd3f13ab7858b0c65</p><p>Network	Ethereum Mainnet</p><p>Block	25,334,592</p><p>Timestamp	Jun-17-2026 03:31:47 AM UTC</p><p>Transaction Type	Type 0 (Legacy)</p><p>Nonce	0</p><p>Gas Limit	21,000</p><p>Gas Used	21,000 / 21,000</p><p>Gas Price	2 Gwei</p><p>Value	0.0082237 ETH</p><p>Input Data	0x</p><p>Status	Failed</p><p>The other failed attempts shared the same structural characteristics: Type 0 transaction format, empty input data, and full gas exhaustion at 21,000.</p><p><strong>Successful Transaction</strong></p><p>Attribute	Value</p><p>Transaction Hash	0x3107a0f3eb2dff2aa37eaf7552527c86171a70227650cfb6543e7c61ee6ae877</p><p>Network	Ethereum Mainnet</p><p>Block	25,334,959</p><p>Timestamp	Jun-17-2026 04:45:11 AM UTC</p><p>Transaction Type	Type 0 (Legacy)</p><p>Nonce	4</p><p>Gas Limit	33,003</p><p>Gas Used	21,055</p><p>Gas Price	4 Gwei</p><p>Value	0.00788 ETH</p><p>Input Data	0x</p><p>Status	Success</p><p><strong>Execution Trace Summary</strong></p><p>Tenderly traces for the failed attempts indicated that execution progressed into the recipient context rather than stopping at the transaction boundary as would typically be expected for a simple legacy EOA transfer. The final observed opcode before exhaustion was PUSH1, which was not itself the cause of failure but the last instruction observed before gas ran out.</p><p>On the successful attempt, the transaction completed normally and consumed 21,055 gas in total.</p><p>State Diff Summary for the Successful Transfer</p><p>The successful transaction produced an expected state transition:</p><p>The recipient balance increased by the transferred amount.</p><p>The sender nonce advanced from 4 to 5.</p><p>The observed state change was consistent with a normal ETH transfer.</p><p>EIP-7702 Context</p><p>Etherscan surfaced MetaMask EIP-7702 delegation metadata associated with the recipient account across the observed transactions. That metadata was visible directly on the transaction detail pages. The report does not independently verify the recipient’s code or delegation state at every relevant block, so it does not claim that the exact account state remained unchanged throughout the sequence. It does, however, document that the same recipient address and the same surfaced delegation metadata were present across the observed transaction set.</p><p><strong><em>Root Cause Assessment</em></strong></p><p>Surface Cause</p><p>Four consecutive transfers failed at the 21,000 gas ceiling.</p><p>Immediate Mechanism</p><p>The transaction required more gas than the sender supplied under the conditions present for the recipient address.</p><p>Most Defensible Interpretation</p><p>The observed transaction pattern is consistent with recipient-side execution associated with an address for which Etherscan surfaced MetaMask EIP-7702 delegation metadata. The successful transfer consumed 21,055 gas, showing that the traditional 21,000 gas heuristic was insufficient in this case.</p><p>What the Evidence Does Not Prove</p><p>The available evidence does not isolate the exact source of the extra 55 gas units, and it does not prove that delegation metadata alone caused the increase. It supports an association, not a fully proven mechanism.</p><p>Alternative Explanations Considered</p><p>Conventional EOA-to-EOA transfer behavior</p><p>Insufficient as a complete explanation, because the failed transfers exhausted all 21,000 gas and the traces indicated recipient-side execution.</p><p>Sender-side execution complexity</p><p>Not supported by the trace evidence, which pointed to failure in the recipient context.</p><p>Network anomaly</p><p>Not evidence of a network anomaly was identified during this investigation. The repeated failure pattern under identical conditions is more consistent with a deterministic cause.</p><p>Tooling error</p><p>Not supported. Etherscan and Tenderly observations were consistent with each other.</p><p>Recipient substitution between attempts</p><p>Not indicated by the transaction history. The recipient address remained the same across the observed sequence.</p><p>Confidence Assessment</p><p>Finding	Confidence</p><p>Recipient-side execution occurred during failed attempts	High</p><p>EIP-7702 delegation metadata was associated with the recipient account	High</p><p>Five sequential attempts were confirmed by nonce progression	High</p><p>Four transfers failed at 21,000 gas and the fifth succeeded at 21,055 gas	High</p><p>Increased gas allocation enabled the successful transfer	High</p><p>Delegated account behavior contributed to the gas deviation	Medium</p><p>Exact source of the additional 55 gas units	Low</p><p><strong><u>Conclusion</u></strong></p><p>This investigation began as an apparent 21,000-gas ETH transfer failure and resolved into a repeatable pattern: four failed transfers at the traditional gas ceiling, followed by a successful fifth transfer after the gas limit was increased. Etherscan surfaced MetaMask EIP-7702 delegation metadata associated with the recipient address, and Tenderly traces showed recipient-side execution during the failures. The successful transfer consumed 21,055 gas, which is above the standard ETH transfer heuristic.</p><p>The evidence supports the conclusion that the 21,000 gas assumption was insufficient for this recipient under the conditions observed. The report does not claim the exact mechanism behind the extra gas consumption, only that the transaction behavior is consistent with recipient-side execution associated with the surfaced delegation metadata.</p><p>On-Chain Evidence</p><p>Etherscan explicitly surfaces the MetaMask EIP-7702 Delegator address (0x63c0c19a282a1B52b07dD5a65b58948A07DAE32B) on the failed transaction detail page, indicating the presence of EIP-7702 delegation metadata on the transaction record at the time it was displayed. The cover image of this article shows this directly — the "Delegated Address" field is visible alongside the 21,000/21,000 gas exhaustion and the [CANCELLED] status.</p><p>Note: Independent verification via eth_getCode at the exact block height of each failed transaction is planned for a follow-up. </p><p>This investigation was completed using Etherscan transaction data and Tenderly execution traces.</p>]]></content:encoded>
            <author>vedinvestigates.xyz@newsletter.paragraph.com (VEDa Investigations)</author>
            <category>ethereum</category>
            <category>eip-7702</category>
            <category>pectra</category>
            <category>blockchain_investigations</category>
            <enclosure url="https://storage.googleapis.com/papyrus_images/7a7f38c715856de9476eaedd41937111633827eb1db1602e9bf53e3ebc2771ad.jpg" length="0" type="image/jpg"/>
        </item>
    </channel>
</rss>