Difference between revisions of "Eth getProof"
Jump to navigation
Jump to search
(Created page with "{{lc}} 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...") |
|||
| Line 1: | Line 1: | ||
{{lc}} | {{lc}} | ||
| + | |||
| + | * https://docs.chainstack.com/reference/getproof | ||
| Line 5: | Line 7: | ||
| + | == See also == | ||
| + | * {{Optimism}} | ||
| + | * {{Erigon}} | ||
| − | + | [[Category:Ethereum]] | |
| − | |||
| − | |||
Revision as of 11:11, 14 June 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.
See also
- 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 - Erigon, Alexey Akhunov, Erigon 3,
eth_getProof, Libmdbx
Advertising:
