-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.3.1 snap sync mode still requires to sync full chain #118
Comments
start of logs:
|
very strange to see this log:
which is for this code:
|
I reproduced the issue locally and will try to find the cause. I will keep you updated on any progress. |
@astudnev Hello, I am sure this issue is caused by the upstream code merge in version 0.3.0 and has been fixed by the upstream code in version v0.4.0. You can avoid this issue by using version v0.4.2 directly. |
According to logs, v0.4.2 syncing using snap method. However it stuck on the following:
not progressing for several hours - is it normal? after that it downloaded pretty fast to 22% and stuck again
it keeps progressing however... |
…access Disable access to pending txs from filters + subscriptions
System information
Network:
mainnet
if you are running a local node, please provide the following information:
op-node version:
op-node 0.3.2
op-geth version:
op-geth 0.3.1
OS & Version: Linux
Expected behaviour
With snap mode it syncs the network in 1 hour as descibed in docs
In base and optimism it really happens this way
Actual behaviour
after downloading headers opbnb starts indexing full chain from 1st block
Steps to reproduce the behaviour
Backtrace
When submitting logs: please submit them as text and not screenshots.
The text was updated successfully, but these errors were encountered: