Open AdamRabbit opened 1 month ago
for custom chain use --state.scheme=hash when init geth init --state.scheme=hash --datadir=/root/datadir /root/config/genesis.json
The database format for go-ethereum changed which is causing this error. If syncing OP Mainnet, you can resync your node with the new format if you would like a smaller database overall or just pass in the legacy flay --state.scheme=path
Hi @dome,
I encounter the same issue, but its not resolved when adding --state.scheme=hash
to the init command.
I'm following the tutorial here : https://docs.optimism.io/builders/chain-operators/tutorials/create-l2-rollup
adding the flag to the geth init command still returns the error:
build/bin/geth init --state.scheme=hash --datadir=datadir genesis.json
...
Fatal: incompatible state scheme, stored: path, provided: hash
any idea? I suppose that the issue lies in the content of my genesis.json file... which I generated with :
go run cmd/main.go genesis l2 \
--deploy-config ../packages/contracts-bedrock/deploy-config/getting-started.json \
--l1-deployments ../packages/contracts-bedrock/deployments/getting-started/.deploy \
--outfile.l2 genesis.json \
--outfile.rollup rollup.json \
--l1-rpc $L1_RPC_URL
thanks a lot!
well my bad, just found out the issue, had to remove the datadir directory and re create a fresh one before doing init again!
I encountered the following error when running Optimism version 1.9.1:
The error was resolved by removing the --gcmode=archive option. After synchronizing the data, transactions are functioning correctly, but there are continuous warning logs like the following:
These warnings appear frequently, generating over 100GB of logs per hour. I want to understand what the issue might be and how to resolve it.