Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement eth_getBlockReceipt API #106

Open
trinhdn97 opened this issue Jul 27, 2024 · 1 comment
Open

Implement eth_getBlockReceipt API #106

trinhdn97 opened this issue Jul 27, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@trinhdn97
Copy link
Contributor

Currently, the way we obtain complete information about all transactions in a block is as follows:

  1. Call eth_getBlockBy{Number,Hash} to retrieve all transaction data for a block;
  2. 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.

@trinhdn97 trinhdn97 added enhancement New feature or request good first issue Good for newcomers labels Jul 27, 2024
@khoau2u
Copy link
Contributor

khoau2u commented Jul 31, 2024

It seems like there are many different implements for this.
I will choose the best and it should be done it by Aug 1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants