You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the way we obtain complete information about all transactions in a block is as follows:
Call eth_getBlockBy{Number,Hash} to retrieve all transaction data for a block;
Iterate through all the transaction data obtained above and call eth_getTransactionReceipt to retrieve the receipt data for each transaction.
This method is highly inefficient for obtaining large amounts of block and transaction data. To make it easier for users, we propose an RPC that returns all the receipt data for a block in one call.
Parity/OpenEthereum (DEPRECATED) has already implemented this method under the parity namespace (parity_getblockreceipts), and some node providers (eg: alchemy eth_getBlockReceipts) have provided similar solutions. If we can include this RPC in the standard, I believe it would be more consistent and user-friendly for users.
The text was updated successfully, but these errors were encountered:
Currently, the way we obtain complete information about all transactions in a block is as follows:
eth_getBlockBy{Number,Hash}
to retrieve all transaction data for a block;eth_getTransactionReceipt
to retrieve the receipt data for each transaction.This method is highly inefficient for obtaining large amounts of block and transaction data. To make it easier for users, we propose an RPC that returns all the receipt data for a block in one call.
Parity/OpenEthereum (DEPRECATED) has already implemented this method under the parity namespace (parity_getblockreceipts), and some node providers (eg: alchemy eth_getBlockReceipts) have provided similar solutions. If we can include this RPC in the standard, I believe it would be more consistent and user-friendly for users.
The text was updated successfully, but these errors were encountered: