Difference between revisions of "Eth getProof"

From wikieduonline
Jump to navigation Jump to search
Line 4: Line 4:
  
  
  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 \

Revision as of 08:29, 14 August 2024


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"}'

See also

Advertising: