Difference between revisions of "Eth getProof"

From wikieduonline
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]

Advertising: