This repository was archived by the owner on Nov 27, 2024. It is now read-only.
Fix alchemy endpoint json rpc parameters#257
Open
IdoBn wants to merge 2 commits intoflashbots:mainfrom
Open
Conversation
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.
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When running the following command (present in the
README.md):We get the following output:
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.