Skip to content
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

finalized_l2 always zero? #240

Open
TurtleSnail opened this issue Feb 4, 2025 · 0 comments
Open

finalized_l2 always zero? #240

TurtleSnail opened this issue Feb 4, 2025 · 0 comments

Comments

@TurtleSnail
Copy link

I am running Optimism mainnet with Erigon node.

curl http://127.0.0.1:9995 -s -X POST -H "Content-Type: application/json"  -d '{"jsonrpc": "2.0","method": "optimism_syncStatus","params": [],"id": 1}' | jq -r '.result | "\(.finalized_l1.number) \(.current_l1.number) \(.finalized_l2.number) \(.unsafe_l2.number)"'
21772487 0 0 131533262

(nb:9995 is node rpc port.)

As you can see;
finalized_l1 looks good.
unsafe_l2 also looks good.

But current_l1 and finalized_l2 are always zero.

I am also running another full node (not archive node) using geth, when i perform the same query, all fields are reported.

Is it a bug? or something else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant