what’s your zcashd.conf?
Just so that I understand what is happening here, can you confirm that the transparent value pool data was visible when using your v5.9.1 zcashd node, but then after you shut down that node and restarted with v5.10.0, it was no longer visible?
That is correct. It worked like a charm on 5.9 but after the 5.10 migration on mainnet. Chainsupply was also missing.
I just triggered the reindexing and the data is back (https://mainnet.zcashexplorer.app/).
This is the full payload with the issue where chainSupply and transparent values are missing:
{
"error": null,
"id": "curltest",
"result": {
"bestblockhash": "0000000001ce4c04e1d1417bd04d1090807f6e7c822fb959582b5ea56ad87d26",
"blocks": 2627003,
"chain": "main",
"chainSupply": {
"monitored": false
},
"chainwork": "00000000000000000000000000000000000000000000000011f567c4b37e2d87",
"commitments": 1546400,
"consensus": {
"chaintip": "c2d6d0b4",
"nextblock": "c2d6d0b4"
},
"difficulty": 60755194.08886648,
"estimatedheight": 2627003,
"headers": 2627003,
"initial_block_download_complete": true,
"pruned": false,
"size_on_disk": 267117118118,
"softforks": [
{
"enforce": {
"found": 4000,
"required": 750,
"status": true,
"window": 4000
},
"id": "bip34",
"reject": {
"found": 4000,
"required": 950,
"status": true,
"window": 4000
},
"version": 2
},
{
"enforce": {
"found": 4000,
"required": 750,
"status": true,
"window": 4000
},
"id": "bip66",
"reject": {
"found": 4000,
"required": 950,
"status": true,
"window": 4000
},
"version": 3
},
{
"enforce": {
"found": 4000,
"required": 750,
"status": true,
"window": 4000
},
"id": "bip65",
"reject": {
"found": 4000,
"required": 950,
"status": true,
"window": 4000
},
"version": 4
}
],
"upgrades": {
"2bb40e60": {
"activationheight": 653600,
"info": "See https://z.cash/upgrade/blossom/ for details.",
"name": "Blossom",
"status": "active"
},
"5ba81b19": {
"activationheight": 347500,
"info": "See https://z.cash/upgrade/overwinter/ for details.",
"name": "Overwinter",
"status": "active"
},
"76b809bb": {
"activationheight": 419200,
"info": "See https://z.cash/upgrade/sapling/ for details.",
"name": "Sapling",
"status": "active"
},
"c2d6d0b4": {
"activationheight": 1687104,
"info": "See https://z.cash/upgrade/nu5/ for details.",
"name": "NU5",
"status": "active"
},
"e9ff75a6": {
"activationheight": 1046400,
"info": "See https://z.cash/upgrade/canopy/ for details.",
"name": "Canopy",
"status": "active"
},
"f5b9230b": {
"activationheight": 903000,
"info": "See https://z.cash/upgrade/heartwood/ for details.",
"name": "Heartwood",
"status": "active"
}
},
"valuePools": [
{
"id": "transparent",
"monitored": false
},
{
"chainValue": 26105.18353761,
"chainValueZat": 2610518353761,
"id": "sprout",
"monitored": true
},
{
"chainValue": 922684.85117737,
"chainValueZat": 92268485117737,
"id": "sapling",
"monitored": true
},
{
"chainValue": 469561.18038181,
"chainValueZat": 46956118038181,
"id": "orchard",
"monitored": true
},
{
"chainValue": 0,
"chainValueZat": 0,
"id": "lockbox",
"monitored": true
}
],
"verificationprogress": 0.9999994790644432
}
}
2 Likes
Okay, thanks, this is interesting. I would have expected a reindex to be required if the data had not been computed before, but if it had been working prior to the upgrade I would not have expected that a reindex was needed to bring it back after the upgrade.
3 Likes
I still get the Internal Servor Error.
Hi,
After reindexing the server, no chainValue and chainValueZat is present.
curl sentence:
curl --user *** --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getblockchaininfo", "params": [] }' -H 'content-type: text/plain;' http://***
Result
{
"result": {
"chain": "main",
"blocks": 2631329,
"initial_block_download_complete": true,
"headers": 2631329,
"bestblockhash": "000000000168ab26a8e29d50201fc4010e81f1d665f9a8353017e1ab6fde3abd",
"difficulty": 78471935.95432323,
"verificationprogress": 0.9999982466914389,
"chainwork": "00000000000000000000000000000000000000000000000011fe5bc719481384",
"pruned": false,
"size_on_disk": 267168270425,
"estimatedheight": 2631329,
"commitments": 1546412,
"chainSupply": {
"monitored": false
},
"valuePools": [
{
"id": "transparent",
"monitored": false
},
{
"id": "sprout",
"monitored": false
},
{
"id": "sapling",
"monitored": false
},
{
"id": "orchard",
"monitored": false
},
{
"id": "lockbox",
"monitored": false
}
],
"softforks": [
{
"id": "bip34",
"version": 2,
"enforce": {
"status": true,
"found": 4000,
"required": 750,
"window": 4000
},
"reject": {
"status": true,
"found": 4000,
"required": 950,
"window": 4000
}
},
{
"id": "bip66",
"version": 3,
"enforce": {
"status": true,
"found": 4000,
"required": 750,
"window": 4000
},
"reject": {
"status": true,
"found": 4000,
"required": 950,
"window": 4000
}
},
{
"id": "bip65",
"version": 4,
"enforce": {
"status": true,
"found": 4000,
"required": 750,
"window": 4000
},
"reject": {
"status": true,
"found": 4000,
"required": 950,
"window": 4000
}
}
],
"upgrades": {
"5ba81b19": {
"name": "Overwinter",
"activationheight": 347500,
"status": "active",
"info": "See https://z.cash/upgrade/overwinter/ for details."
},
"76b809bb": {
"name": "Sapling",
"activationheight": 419200,
"status": "active",
"info": "See https://z.cash/upgrade/sapling/ for details."
},
"2bb40e60": {
"name": "Blossom",
"activationheight": 653600,
"status": "active",
"info": "See https://z.cash/upgrade/blossom/ for details."
},
"f5b9230b": {
"name": "Heartwood",
"activationheight": 903000,
"status": "active",
"info": "See https://z.cash/upgrade/heartwood/ for details."
},
"e9ff75a6": {
"name": "Canopy",
"activationheight": 1046400,
"status": "active",
"info": "See https://z.cash/upgrade/canopy/ for details."
},
"c2d6d0b4": {
"name": "NU5",
"activationheight": 1687104,
"status": "active",
"info": "See https://z.cash/upgrade/nu5/ for details."
}
},
"consensus": {
"chaintip": "c2d6d0b4",
"nextblock": "c2d6d0b4"
}
},
"error": null,
"id": "curltest"
}
Config file:
addnode=mainnet.z.cash
txindex=1
insightexplorer=1
experimentalfeatures=1
rpcport=***
rpcuser=***
mainnet=1
rpcpassword=***
#proxy=127.0.0.1:9050
paymentdisclosure=1
rpcallowip=***
I’m working on skipping chainValue rendering on the UI
1 Like
The workaround is live. This is not permanent.
Do you know why chainvalues are not resolved by rpc request?
FYI, I updated both my raspi node and my local computer node to 5.10 and they both show the correct info:
Do you think its because the zcashblockchain package is not accounting for the new lockbox id ?
edit: I was wrong, it seems to be working locally fine:
My version looks slightly different from yours, are you running a docker version by chance? Perhaps the error is there.
2 Likes
i have been testing with zingo-cli on TestNet. since the update i have not confirmed any transactions 
also this testnet faucet is down as of this moment: https://faucet.zecpages.com/
1 Like
CC @BrunchTime
Same here, everything fine. Can you confirm your curl result and your runtime is/was pointed at the right conf? Strange error
Thanks for the ping.
I ran into a zcashd build error in Ubuntu, not sure what’s officially supported at this point. I don’t really have time to work through it, so I simply took the faucet down for now. I may deploy it afresh sometime in a supported environment, but I don’t have a solid timeline. Seeing some user demand from @fluidvanadium is motivation! 
1 Like
Ill set up a zebra miner if you have a tazzy
1 Like
Yeah, I ran into the same issue with my version of Ubuntu awhile back. I don’t upgrade/update often enough…
1 Like
If anyone wants TAZ, just send me your address.
Edit: my testnet node is not syncing so I can’t currently send TAZ to anyone.
1 Like
You will need to be validating using the new consensus branch ID, at very least.
Is there a way to sync quickly for a testnet node. I missed the testnet node upgrade. Or is the only way to just restart the node and it will resync from genesis?
1 Like
zcashd or zebrad? If it’s zebrad we have instructions in the release notes Release Zebra 1.9.0 · ZcashFoundation/zebra · GitHub
But yes, wiping the state and resyncing from genesis would also work.
1 Like
This would be for zcashd
1 Like