Closed moorow closed 2 months ago
Based on some discussion on Discord it looks like this may be related to Path Based (PBSS)?
Someone said that this only affects Full nodes, not Archive.
INFO [08-30|09:27:51.974] State schema set to default scheme=path
This line was printed in the logs
Thanks for the flag, can you share your runtime configuration you're using for op-mode and op-geth?
Sure thing:
op-geth
- --ws
- --ws.port=8550
- --ws.addr=0.0.0.0
- --ws.origins="*"
- --http
- --http.port=8549
- --http.addr=0.0.0.0
- --http.vhosts="*"
- --http.corsdomain="*"
- --authrpc.addr=0.0.0.0
- --authrpc.jwtsecret=/data/jwt.txt
- --authrpc.port=9333
- --authrpc.vhosts="*"
- --datadir=/data/geth
- --verbosity=3
- --rollup.disabletxpoolgossip=true
- --rollup.sequencerhttp=https://mainnet-sequencer.optimism.io
- --op-network=op-mainnet
- --syncmode=snap
- --rpc.gascap=0
- --rpc.evmtimeout=10s
- --rpc.batch-response-max-size=50000000
- --rpc.batch-request-limit=2000
- --nat=extip:${HOST_IP_ADDRESS}
op-node
- --l1=${L1_EXECUTION_RPC_URL}
- --l1.rpckind=alchemy
- --l1.trustrpc
- --l1.beacon=${L1_BEACON_RPC_URL}
- --l2=ws://op-geth:9333
- --network=op-mainnet
- --rpc.addr=127.0.0.1
- --rpc.port=9545
- --l2.jwt-secret=/data/jwt.txt
- --syncmode=execution-layer
- --p2p.advertise.ip=${HOST_IP_ADDRESS}
- --p2p.listen.ip=0.0.0.0
- --p2p.listen.tcp=9003
- --p2p.listen.udp=9003
- --p2p.advertise.tcp=9003
- --p2p.advertise.udp=9003
- --metrics.enabled
- --metrics.addr=0.0.0.0
- --metrics.port=7300
Discussed in https://github.com/ethereum-optimism/developers/discussions/564