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
please. When will the result value output the desired value instead of 0x0? #29442
Comments
Once the initial sync is done, |
@MariusVanDerWijden
However, it seems like blocks continue to be received from CL. However, the eth_blockNumber value is still 0x0. |
|
@rjl493456442 |
Exactly
Thanks and Best regards Gary rong
junghyun0783 ***@***.***>于2024年4月3日 周三下午3:40写道:
… @rjl493456442 <https://github.com/rjl493456442>
First of all, thank you for your reply.
Should all synchronizations be completed even though syncmode is "snap"?
—
Reply to this email directly, view it on GitHub
<#29442 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNO6OITASEFDIJS2KKMIKTY3OW5JAVCNFSM6AAAAABFUKSMYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZTG44DCMZXGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The initialization process is complete.
|
You're only connected to one peer, and geth is busy trying to sync state. Having only one peers makes it go very slow (its not even certain that the singular peer you have is capable of serving state). Your node is starving, and unable to progress in the sync |
@holiman please. help. |
It can also be related to the fact that Sepolia is not a very active network with fewer peers? |
@fjl |
hello.
I really want to hear the answer I want.
This is the current result when calling eth_syncing RPC.
When calling eth_blockNumber RPC, the result value continues to be 0x0.
What I want is when the result value will be output as a block number rather than 0x0. I kept asking this, but he gave me a different answer and said "close".
please. When will the result value output the desired value instead of 0x0?
The text was updated successfully, but these errors were encountered: