Miners

May 6 news, Bitcoin Core developers have decided to remove the restrictions on transaction data in the next network upgrade, allowing more data to be included in a more efficient manner. Bitcoin developer Greg Sanders announced on GitHub on May 5: "The next version of Bitcoin Core will by default relay and mine transactions with OP_RETURN outputs exceeding 80 bytes and allow any number of outputs." In response, critics argue that the proposal was made without proper consensus procedures. Marty Bent, managing partner of Ten31 Fund, stated: "There is currently no consensus on the OP_RETURN issue." Reportedly, OP_RETURN allows transaction outputs that store small amounts of data on the blockchain, which became popular during the Bitcoin ordinal craze in early 2024. Unlike regular transaction outputs, OP_RETURN outputs are unspendable and do not increase unspent transaction outputs (UTXO). (Cointelegraph)

On May 6, Ethereum developer @nero_eth published an article discussing the "Delayed Execution and Free DA Issue." Delayed execution (EIP-7886) changes the verification process: validators certify block validity through pre-checks (such as nonce and balance) before transactions are fully executed. If a transaction fails due to insufficient balance during execution (for example, transaction A depletes account B's balance, causing B's transaction B to be unable to pay for Gas), its data is already written into the block and processed by validators, but no fees are paid. This leads to the Free DA issue: invalid transactions occupy on-chain data availability resources, and validators are not compensated. The article proposes four solutions: optimistic certification, pre-validation and pre-charging, pre-charging entities, and no-operation on the execution layer. These solutions ensure that data writing incurs costs through pre-deducting fees, block reorganization, or state rollback, preventing network congestion and economic unfairness caused by Free DA.