-
Notifications
You must be signed in to change notification settings - Fork 44
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
Centralized RPC Providers #9
Comments
Try this one liner from the console to see if it's working yet. Or "http://mainnet.infura.io" with whatever URL you want to test:
|
feat: add resources for documentation driven development
wow! looks like infura finally supports it! |
note to self: update readme then close issue |
How do I know what params to send to get the data of a specific block? This request works, but I have no clue how to construct the params, and getProof is nowhere to be found in infuras own documentation. I assume "latest" can be replaced by a specific block number, but how do I know which key to use? |
The above curl request is just for troubleshooting that your connection is working. Please read the API for this JS module. It does not require the same arguments. |
edit
fixed! infura now supports this
At time of this writing neither Infura nor any RPC provider's support
eth_getProof
, but infura should in the very near future. ETC chain supports the call iff using multigeth, but against no service central services are known to be running it.Implications
getting storage Proofs and Account proofs wont work unless your RPC provider supports
eth_getProof
. Solution is to run geth/parity-ethereum/multigeth locally for those Additionally it needs to be a full or archive node if you want to get historic proofs.The text was updated successfully, but these errors were encountered: