I didn’t want to reveal publicly where my node is stuck. Besides the embarrassment, it is a network privacy issue: I may be the only node in the world now stuck at this height. But for the greater good… sigh.
As of block height 1715985, block timestamp 2022-06-25 22:50:44 (
), the getblockchaininfo and gettxoutsetinfo RPCs tell me the following about Zcash’s supply:
| Value Pool | ZEC |
|---|---|
| Transparent | 11,751,562.60778898 |
| Orchard | 9,523.68925908 |
| Sapling | 802,836.08938170 |
| Sprout | 28,165.27842336 |
| Total | 12,592,087.66485312 |
@noamchom, what does your node tell you? If you’ve got a twitter or something, please ask @cz_binance why his CMC site is FUDding the Zcash supply.
Click to expand:
Show your work!
nullius@zcash:~$ zcash-cli getblockchaininfo
{
"chain": "main",
"blocks": 1715985,
"initial_block_download_complete": false,
"headers": 1715985,
"bestblockhash": "000000000198bdd5446ff5a0ca08b59940b9c68e24a831c0e3594c39071f8f98",
"difficulty": 73467160.93973005,
"verificationprogress": 0.9788401600916485,
"chainwork": "000000000000000000000000000000000000000000000000099c14b2e928d79f",
"pruned": false,
"size_on_disk": 39112797667,
"estimatedheight": 1750720,
"commitments": 1545080,
"valuePools": [
{
"id": "sprout",
"monitored": true,
"chainValue": 28165.27842336,
"chainValueZat": 2816527842336
},
{
"id": "sapling",
"monitored": true,
"chainValue": 802836.08938170,
"chainValueZat": 80283608938170
},
{
"id": "orchard",
"monitored": true,
"chainValue": 9523.68925908,
"chainValueZat": 952368925908
}
],
"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"
}
}
nullius@zcash:~$ zcash-cli gettxoutsetinfo
{
"height": 1715985,
"bestblock": "000000000198bdd5446ff5a0ca08b59940b9c68e24a831c0e3594c39071f8f98",
"transactions": 1804723,
"txouts": 21261303,
"bytes_serialized": 588650026,
"hash_serialized": "f65b708a9eb1818486130b1bc313030a2e819e3827a481e9126d1705fbd66334",
"total_amount": 11751562.60778898
}
nullius@zcash:~$ bc -sql
11751562.60778898 + 9523.68925908 + 802836.08938170 + 28165.27842336
12592087.66485312
If you have a healthy node running at the current chain tip, I don’t believe there is any privacy problem with sharing your results here.
/* XXX TODO */ When I am up and running again, adapt some tricks I know for auditing the Bitcoin supply to accounting for each and every zat here.