According to Foresight News, the Ethereum Foundation has issued a reminder regarding recent issues faced by some Layer 2 deployments on Sepolia. These problems arose due to changes in proof formats introduced by EIP-7549. In response to the Fusaka incident, all Blob initiators are urged to update their software to create Cell Proofs instead of Blob Proofs.
A significant change in EIP-7549 allows for the download of specific parts of a Blob rather than the entire Blob, facilitating data availability sampling. While signed transactions remain valid, Cell Proofs need to be recalculated. Some clients, particularly go-ethereum, will handle this conversion in the eth_sendTransaction and eth_sendRawTransaction RPCs, with the process expected to take about a second. Consequently, Blob transaction initiators are advised to switch to Cell Proofs promptly to reduce overhead at the RPC level.
Transactions in the pool at the time of the fork may be discarded by some implementations, while others will convert them to Cell Proofs. If transactions are not included in the blockchain post-fork, it is recommended to resend them using Cell Proofs. Certain implementations allow Blob Proof transactions to continue propagating for a few minutes after the hard fork to ensure network stability.
Blob transaction initiators, such as Layer 2 solutions, should update their transaction sending code to generate Cell Proofs. All major client libraries offer the functionality to create these proofs through ComputeCellsAndKZGProofs(), applicable to all major programming languages.