eth_blockNumber() seems to be broken when geth is in --fast mode
Closed this issue · 4 comments
not sure if this is a geth issue or yours.
while running geth with --rpc and --fast, eth_blockNumber() always returns zero.
@paulohm2 This sounds like a geth issue. Does it only happen while the chain is syncing, or even after it has finished syncing?
Didnt try it when the syncing has finished, only during the syncing process.
On Sun, Aug 7, 2016 at 12:13 AM, Maurycy notifications@github.com wrote:
@paulohm2 https://github.com/paulohm2 This sounds like a geth issue.
Does it only happen while the chain is syncing, or even after it has
finished syncing?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#15 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT5sLbaUULkFdKSBtIINVgr4alCxV7T5ks5qdU0_gaJpZM4JeKcl
.
Paulo Mannheimer
Instant Solutions - Aproximando Empresas e Clientes
+55 11 4063.6100
+55 21 4063.6100
+55 61 4063.6100
www.instant.com.br
just confirmed that it only happens while geth is syncing. When syncing is done it returns OK
print c.eth_blockNumber()
2127676
will open a geth report and see what they say.