Skip to content
This repository has been archived by the owner on Nov 27, 2024. It is now read-only.

Fix alchemy endpoint json rpc parameters #257

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

IdoBn
Copy link

@IdoBn IdoBn commented Feb 4, 2022

When running the following command (present in the README.md):

./mev inspect 12914944

We get the following output:

Inspecting block 12914944
Skipping virtualenv creation, as specified in config file.
ERROR:mev_inspect.retry:Request for method eth_getBlockReceipts, params: (12914944,), retrying: 0/5
ERROR:mev_inspect.retry:Request for method eth_feeHistory, params: (1, '0xc51100', None), retrying: 0/5
ERROR:mev_inspect.retry:Request for method eth_feeHistory, params: (1, '0xc51100', None), retrying: 1/5
ERROR:mev_inspect.retry:Request for method eth_getBlockReceipts, params: (12914944,), retrying: 1/5

These errors are a result of bad parameters passed to the json-rpc endpoint on some nodes. In my case this was an alchemy node.

IdoBn added 2 commits February 4, 2022 20:10
It appears that some json-rpc endpoints, from my testing it appears
that alchemy is one of them require the get_block_receipts json-rpc
to have receive the block number as a hex value.
It appears that fee_history must receive an array as the third parameter
and it's default None value does not work with some json-rpc nodes.
@maxholloway
Copy link
Contributor

In the README it says that the RPC node must support erigon traces and receipts. Does alchemy support erigon receipts? If not, you might try making an RPC endpoint through pokt.network.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants