You would need to run zcashd with the reindex flag in order to specify rebuilding the database. Otherwise yes, it will just pick up where it left off.
zcashd
computes and stores deltas for each block (i.e. ZEC added to or removed from a given pool). The chain values are computed dynamically in-memory as the sum of all deltas along a given chain. This happens initially on start, and then incrementally as new blocks are added.
If you see monitored: false
at a given block height, that means somewhere in the chain prior to that height, there is a block missing either a delta or an in-memory chain value, which means all subsequent blocks cannot have in-memory chain values computed even if they have deltas. Finding where that happened is therefore useful to determining where a bug might be hiding.
@Cacho assuming this is still happening for you, can you please bisect your local nodeās state with getblock HEIGHT
? That is:
- Use
getblockchaininfo
to confirm the bug is still occurring. - Take the value from the
blocks
field of its output asBAD_HEIGHT
, and callgetblock BAD_HEIGHT
; you should see the same missing information. - Compute
NEXT_HEIGHT = BAD_HEIGHT / 2
and callgetblock NEXT_HEIGHT
.- If that also doesnāt show chain values, then set
BAD_HEIGHT = NEXT_HEIGHT
and then repeat the above. - If that does show chain values, then call that
GOOD_HEIGHT
, computeNEXT_HEIGHT = (BAD_HEIGHT - GOOD_HEIGHT) / 2 + GOOD_HEIGHT
, and then callgetblock
again.
- If that also doesnāt show chain values, then set
You should find the problematic height in around 22 getblock
calls.
Hi,
It looks like the block 2630586 is the issue
zcashd@node:~$ curl --user xxx--data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getblock", "params": ["2630585"] }' -H 'content-type: text/plain;' http://xxx:28233 | jq '.result.valuePools[0].chainValue'
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 4983 100 4902 100 81 1245k 21082 --:--:-- --:--:-- --:--:-- 1622k
13989930.17876866
zcashd@node:~$ curl --user rxxx --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getblock", "params": ["2630586"] }' -H 'content-type: text/plain;' http://xx:28233 | jq '.result.valuePools[0].chainValue'
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 4825 100 4744 100 81 194k 3406 --:--:-- --:--:-- --:--:-- 204k
I see the same transparent chainValue
as you at height 2630585, and for height 2630586 my zcashd
node has a transparent chainValue
of 13989933.30381866 (and a delta of 3.12505000).
I restarted my zcashd
node to 5.10.0 on 2024-08-28, and my node scanned the block at height 2630586 on 2024-08-31. So the block itself canāt be inherently incompatible; more likely the order in which the block was received from the network may make a difference.
@Cacho something that is not clear from your previous messages: is your node still reindexing? Can you recheck block 2630586 and see if it is showing chain value information now?
The node is not reindexing. IĀ“m still not seeing ahy chainValue 2630586 block
screenshots?
Hi, is the zcash testnet chain stuck?
My upgraded nodes (5.10.0) are stuck at 2996479
ā¦ also at startup I see some of the peers are also stuckā¦
2024-09-17T06:25:14.496572Z INFO main: receive version message: /Zebra:1.9.0/: version 170110, blocks=2996479, us=51.195.63.10:30835, peer=3
And ā¦ the explorer is also stuck!
https://testnet.zcashexplorer.app/blockchain-info
Anyway to fix?
My node is also stuck but on height 2996477. Iām reaching out to people on the R&D Discord and weāre looking into it also.
Is it a public discord? Can I join? Could you please share a link, if yes?
Invite link is here Zcash R&D Chat Server Launch!
BTW part of the problem was simply lack of miners. Iām currently mining with my local node but itās not always up. We are looking into deploying long-running miners.
The zcashexplorer.app issue seems different though since itās stuck at a lower height.
Does that mean with your local miner, your node has moved up from 2996477
? Whatās its status now?
zebrad appears to be running, currently 2998269. zcashd is lagging behind, may or may not be stuck at 2998183
Yes, Iām at 2998320