Difference between revisions of "Eth getProof"
Jump to navigation
Jump to search
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{lc}} | {{lc}} | ||
| + | <code>eth_getProof</code> | ||
* https://docs.chainstack.com/reference/getproof | * https://docs.chainstack.com/reference/getproof | ||
| − | if you're running an Erigon Ethereum [[execution client]] for your L1 provider you will need to include --l1.trustrpc. At the time of writing, Erigon doesn't support the eth_getProof that we prefer to use to load L1 data for some processing in op-node. The trustrpc flag makes it use something else that erigon supports, but the op-node can't verify for correctness. | + | if you're running an Erigon Ethereum [[execution client]] for your L1 provider you will need to include [[--l1.trustrpc]]. At the time of writing, Erigon doesn't support the eth_getProof that we prefer to use to load L1 data for some processing in [[op-node]]. The trustrpc flag makes it use something else that erigon supports, but the op-node can't verify for correctness. |
curl https://ethereum.end.point.example \ | curl https://ethereum.end.point.example \ | ||
| Line 10: | Line 11: | ||
-H "[[Content-Type: application/json]]" \ | -H "[[Content-Type: application/json]]" \ | ||
--data '{"method":"[[eth_getProof]]","params":["0x4200000000000000000000000000000000000016",[],"0x123456"],"id":1,"jsonrpc":"2.0"}' | --data '{"method":"[[eth_getProof]]","params":["0x4200000000000000000000000000000000000016",[],"0x123456"],"id":1,"jsonrpc":"2.0"}' | ||
| + | |||
| + | == Related == | ||
| + | * [[Merkle]] | ||
| + | * [[Proof]] | ||
| + | * [[Unknown block]] | ||
== See also == | == See also == | ||
| + | * {{eth api}} | ||
* {{Optimism}} | * {{Optimism}} | ||
* {{Erigon}} | * {{Erigon}} | ||
[[Category:Ethereum]] | [[Category:Ethereum]] | ||
Latest revision as of 13:14, 17 September 2024
eth_getProof
if you're running an Erigon Ethereum execution client for your L1 provider you will need to include --l1.trustrpc. At the time of writing, Erigon doesn't support the eth_getProof that we prefer to use to load L1 data for some processing in op-node. The trustrpc flag makes it use something else that erigon supports, but the op-node can't verify for correctness.
curl https://ethereum.end.point.example \ -X POST \ -H "Content-Type: application/json" \ --data '{"method":"eth_getProof","params":["0x4200000000000000000000000000000000000016",[],"0x123456"],"id":1,"jsonrpc":"2.0"}'
Related[edit]
See also[edit]
- Ethereum API, 8545,
eth_call, eth_blockNumber, eth_getBalance, eth_getBlockByNumber, eth_getTransactionReceipt, web3_clientVersion, eth_subscribe, /eth/v1/node/syncing,cast,eth_getProof,eth_call, eth_chainId, eth_getBlockReceipts, Eth Beacon Node API,eth_sendRawTransaction, eth_getLogs,geth --http.api - Optimism,
OP, OP Stack, OP Architecture,op-, Superchain, Optimism Bedrock, Proxyd, Crypto sequencer, rollup, Optimistic Rollup Protocol, Optimism Blobs, Optimism monitorism, fault-mon,eth-optimism/sdk,L2OutputOracle.sol, OptimismPortal.sol, OP Sepolia Testnet (11155420), OP Labs, Optimism Foundation, Fault Proof, Ecotone, Fjord, Rollup node, L2 Chain Derivation Specification, Fastnode.io, OP Contracts Manager (OPCM) - Erigon, Alexey Akhunov, Erigon 3,
eth_getProof, Libmdbx
Advertising:
