smartcontracts/simple-optimism-node

Always several hundred blocks behind

Closed this issue · 5 comments

I have been in sync node for several weeks.

image

my env file

# Network to run the node on ("mainnet" or "goerli")
NETWORK_NAME=mainnet

# Type of node to run ("full" or "archive"), note that "archive" is 10x bigger
NODE_TYPE=full

###############################################################################
#                            �~F~S REQUIRED (LEGACY) �~F~S                            #
###############################################################################

# Where to sync data from ("l1" or "l2"), see README
SYNC_SOURCE=l1

# Reference L2 node to run healthcheck against
HEALTHCHECK__REFERENCE_RPC_PROVIDER=https://opt-mainnet.g.alchemy.com/v2/
# L1 node to run fault detection against
FAULT_DETECTOR__L1_RPC_PROVIDER=https://eth-mainnet.g.alchemy.com/v2/
# Node to get chain data from (if SYNC_SOURCE is "l1" then use L1 node, etc.)
DATA_TRANSPORT_LAYER__RPC_ENDPOINT=http://192.168.2.36:54102

###############################################################################
#                            �~F~S REQUIRED (BEDROCK) �~F~S                           #
###############################################################################

# Where to get the Bedrock database ("download" or "migration"), see README
BEDROCK_SOURCE=download

# L1 node that the op-node (Bedrock) will get chain data from
OP_NODE__RPC_ENDPOINT=http://192.168.2.36:54102

# Type of RPC that op-node is connected to, see README
OP_NODE__RPC_TYPE=basic

Should i update SYNC_SOURCE to l2?

set SYNC_SOURCE to l2 have the same issue

官方限速,请使用第三方公共节点

unek commented

bumping - possibly related to #78? anyone tried op-geth with --snapshot=false?

I don't think that one is quite resolved

unek commented

Still not resolved.