You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you running the most up to date node software?
Yes
Did you check the documentation?
Yes
Did you check for duplicate questions?
Yes
Issue Description
I'm syncing my Optimism Node using the snap sync mode and my own Ethereum node with Nethermind as Execution client and Lighthouse as Consensus client as my L1 node for op-node.
I wasn't able to get op-node to sync without adding the --l1.trustrpc=true flag which seems odd since Nethermind supports eth_getProof. https://docs.nethermind.io/interacting/json-rpc-ns/eth/#eth_getproof
My node is fully synced and I use it to run transactions without any problem.
Protocol Description
op-geth version: op-geth version 0.1.0-unstable-0402d543-20240222
op-node version: op-node version v0.0.0-c87a469d-1709078315
I'm seeing this warning in op-node but I'm not sure it is related to this issue: Mar 19 18:59:28 ethereumonarm-orangepi5-plus-47e837727 op-node[2461]: t=2024-03-19T18:59:28+0000 lvl=warn msg="Derivation process temporary error" attempts=1 err="engine stage failed: temp: failed to fetch blobs: failed to get blob sidecars for L1BlockRef 0x8a7d9d44378f054bdfc72eebd3b3c602adddd46d89012e9eb7f5b49d10a51996:19463742: failed to fetch blob sidecars for slot 8663825 block 0x8a7d9d44378f054bdfc72eebd3b3c602adddd46d89012e9eb7f5b49d10a51996:19463742: failed request with status 404: {\"code\":404,\"message\":\"NOT_FOUND: beacon block at slot 8663825\",\"stacktraces\":[]}"
node-operatorQuestions relating to running a rollup node on OP Mainnet/Testnet.discussion-metricsUsed by Github Action to gather discussion metrics on the question and answer section.
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Are you running the most up to date node software?
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
I'm syncing my Optimism Node using the snap sync mode and my own Ethereum node with Nethermind as Execution client and Lighthouse as Consensus client as my L1 node for op-node.
I wasn't able to get op-node to sync without adding the
--l1.trustrpc=true
flag which seems odd since Nethermind supportseth_getProof
.https://docs.nethermind.io/interacting/json-rpc-ns/eth/#eth_getproof
My node is fully synced and I use it to run transactions without any problem.
Protocol Description
op-geth version:
op-geth version 0.1.0-unstable-0402d543-20240222
op-node version:
op-node version v0.0.0-c87a469d-1709078315
Network name: Optimism
ChainID: 10
L1 chain: Ethereum Mainnet
op-geth config:
ARGS='--ws --op-network=op-mainnet --ws.port=8546 --ws.addr=localhost --ws.origins="*" --http --http.port=8545 --http.addr=localhost --http.vhosts="*" --http.corsdomain="*" --authrpc.addr=localhost --authrpc.jwtsecret=/etc/ethereum/jwtsecret --authrpc.port=8551 --authrpc.vhosts="*" --datadir=/home/ethereum/.op-geth --verbosity=3 --rollup.disabletxpoolgossip=true --rollup.sequencerhttp=https://mainnet-sequencer.optimism.io --rollup.historicalrpc=https://mainnet.optimism.io --syncmode=snap'
op-node config:
ARGS="--l1=http://192.168.1.150 --l1.rpckind=nethermind --l1.beacon=http://192.168.1.150:5052 --l1.trustrpc=true --l2=http://localhost:8551 --network=op-mainnet --rpc.port=9545 --l2.jwt-secret=/etc/ethereum/jwtsecret --p2p.priv.path=/home/ethereum/.op-node/opnode_p2p_priv.txt --p2p.peerstore.path=/home/ethereum/.op-node/opnode_peerstore_db --p2p.discovery.path=/home/ethereum/.op-node/opnode_discovery_db --metrics.enabled --syncmode=execution-layer --rollup.load-protocol-versions=true --rollup.halt=major"
Node Logs
I'm seeing this warning in op-node but I'm not sure it is related to this issue:
Mar 19 18:59:28 ethereumonarm-orangepi5-plus-47e837727 op-node[2461]: t=2024-03-19T18:59:28+0000 lvl=warn msg="Derivation process temporary error" attempts=1 err="engine stage failed: temp: failed to fetch blobs: failed to get blob sidecars for L1BlockRef 0x8a7d9d44378f054bdfc72eebd3b3c602adddd46d89012e9eb7f5b49d10a51996:19463742: failed to fetch blob sidecars for slot 8663825 block 0x8a7d9d44378f054bdfc72eebd3b3c602adddd46d89012e9eb7f5b49d10a51996:19463742: failed request with status 404: {\"code\":404,\"message\":\"NOT_FOUND: beacon block at slot 8663825\",\"stacktraces\":[]}"
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions