# Zcash Blockchain Size—Risks?

**URL:** <https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126>\
**Category:** General\
**Created:** [October 7, 2022, 8:27pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126 "2022-10-07T20:27:39Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![hanh](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/hanh/32/27853_2.png) [@hanh](https://forum.zcashcommunity.com/u/hanh)\
**Post date:** [February 11, 2023, 9:05pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/43 "2023-02-11T21:05:46Z")

</div>

> [@dismad](#):
>
> Some like to complain about blockchain size but how much does it really [matter](https://www.newegg.com/seagate-model-sthp4000400-4tb/p/1Z4-002P-00VC9?Item=9SIBHNKJGE8459&Description=external%20Hardd%20rive&cm_re=external_Hardd%20rive-_-1Z4-002P-00VC9-_-Product&quicklink=true)? 😏

Well… It matters since the node count drop is happening. How else would you explain it?

Even if it is possible to run a node with a RPI and an external hd, the amount of time and effort required is extremely high and only dedicated Zcash supporters are going to go through.

Not to mention the ongoing bandwidth requirements.

Please, let’s recognize the Blockchain size is a problem for 99% of the people

---

<div class="post-metadata">

**Author:** ![dismad](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/dismad/32/18432_2.png) [@dismad](https://forum.zcashcommunity.com/u/dismad)\
**Post date:** [February 12, 2023, 7:05am UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/44 "2023-02-12T07:05:39Z")

</div>

> [@curiouschipmunk](#):
>
> At what point will node operators begin experiencing failures and/or stop supporting Zcash due to the size of the chain?

> [@hanh](#):
>
> It matters since the node count drop is happening. How else would you explain it?

Let’s imagine we _could_ prune the node. Uneducated folks, the 99 % you mention, _still_ wouldn’t run nodes because, IMHO, the issue isn’t size. So my answer to curiouschipmunk is I’m not sure the rate of change with respect to the size of the blockchain will ever overtake the (negative) rate of change in price of hardware that is needed to run it.

Should we optimize to be as small (size) and fast (sync) as as possible? Yes.  
Do some folks in the community love to point out the spam / size / [insert new bad metric here] ? Also yes.

I just don’t see the risk though relative to other things. Appreciate your thoughts.

---

<div class="post-metadata">

**Author:** ![hanh](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/hanh/32/27853_2.png) [@hanh](https://forum.zcashcommunity.com/u/hanh)\
**Post date:** [February 12, 2023, 8:25am UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/45 "2023-02-12T08:25:47Z")

</div>

> [@dismad](#):
>
> So my answer to curiouschipmunk is I’m not sure the rate of change with respect to the size of the blockchain will ever overtake the (negative) rate of change in price of hardware that is needed to run it.

The blockchain size impacts more than the cost of the hardware. Bandwidth and time matter too. The fact that this is caused by useless spam and not valuable transactions somewhat exacerbate me. I think it’s harder to feel part of a mission when this mission is now mainly relaying and storing someone’s spam.

---

<div class="post-metadata">

**Author:** ![tokidoki](https://avatars.discourse-cdn.com/v4/letter/t/dc4da7/32.png) [@tokidoki](https://forum.zcashcommunity.com/u/tokidoki)\
**Post date:** [February 12, 2023, 8:46am UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/46 "2023-02-12T08:46:01Z")

</div>

> [@hanh](#):
>
> this is caused by useless spam and not valuable transactions

I think there’s no way to tell that the shielded transactions with hundreds of sender/recipients are “useless” or not. Though I agree that the blockchain size may deter a lot of people from using Zcash (in its current design and bandwidth requirement) let alone run a Zcash full node.

---

<div class="post-metadata">

**Author:** ![Autotunafish](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/autotunafish/32/7827_2.png) [@Autotunafish](https://forum.zcashcommunity.com/u/Autotunafish)\
**Post date:** [February 12, 2023, 2:27pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/47 "2023-02-12T14:27:15Z")

</div>

Just to be clear, there is already a prune option for zcashd but it disables the internal wallet and is incompatible with txindex flag. Ive never run a zcashd node like that before however so I don’t have any first-hand experience

---

<div class="post-metadata">

**Author:** ![dismad](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/dismad/32/18432_2.png) [@dismad](https://forum.zcashcommunity.com/u/dismad)\
**Post date:** [February 12, 2023, 5:12pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/48 "2023-02-12T17:12:10Z")

</div>

> [@tokidoki](#):
>
> I think there’s no way to tell that the shielded transactions with hundreds of sender/recipients are “useless” or not.

Would be wild if it came out “the spam” was an unannounced application.

> [@hanh](#):
>
> I think it’s harder to feel part of a mission when this mission is now mainly relaying and storing someone’s spam.

I hear you and appreciate your honesty. Solutions are coming ♥

---

<div class="post-metadata">

**Author:** ![noamchom](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/noamchom/32/20269_2.png) [@noamchom](https://forum.zcashcommunity.com/u/noamchom)\
**Post date:** [February 13, 2023, 3:07pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/49 "2023-02-13T15:07:19Z")

</div>

> [@hanh](#):
>
> I think it’s harder to feel part of a mission when this mission is now mainly relaying and storing someone’s spam.

I second the notion, and many other points above. The ongoing blockchain spam event is very bad for Zcash and the longer it goes on without mitigation it makes our community and developers appear hapless in the face of a severe challenge like this. The drop in node count is highly correlated to the spamming which leads me to conclude the same as others, that prior validators have thrown in the towel on supporting the Zcash network.

Is there any material timeline for when the spamming will be defended against by a technical upgrade to the protocol?

---

<div class="post-metadata">

**Author:** ![gottabeJay](https://avatars.discourse-cdn.com/v4/letter/g/96bed5/32.png) [@gottabeJay](https://forum.zcashcommunity.com/u/gottabeJay)\
**Post date:** [February 13, 2023, 8:49pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/50 "2023-02-13T20:49:18Z")

</div>

Mina has a tiny ‘chain’. Its 22kb. Its a snapshort of the chain. Its possible with recursive zkSNARKS to _compress_ Zcash. The bloat will stay but its possible the reduce the size of the chain.

The spam is a problem. The bloat is a problem. Light wallet sync is a problem. We got to fix it. Fast. Its a deadweight on Zcash. It affects everyone and everything.

---

<div class="post-metadata">

**Author:** ![noamchom](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/noamchom/32/20269_2.png) [@noamchom](https://forum.zcashcommunity.com/u/noamchom)\
**Post date:** [February 15, 2023, 2:47pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/51 "2023-02-15T14:47:28Z")

</div>

@steven-ecc @nathan-at-least

Can anyone who provided technical updates above, share a current update from down in the trenches? We haven’t received any follow up to this thread since Oct-Nov 2022 from ECC, ZF, or any other team, and we can all see that the issue remains unsolved. The last couple dozen comments have been speculative, opinion, or wandering off topic. Thx!

---

<div class="post-metadata">

**Author:** ![Autotunafish](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/autotunafish/32/7827_2.png) [@Autotunafish](https://forum.zcashcommunity.com/u/Autotunafish)\
**Post date:** [February 15, 2023, 3:02pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/52 "2023-02-15T15:02:03Z")

</div>

Steven isn’t at ECC since late last year I think, you’d wanna ask someone else

---

<div class="post-metadata">

**Author:** ![dontpanicburns](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/dontpanicburns/32/32565_2.png) [@dontpanicburns](https://forum.zcashcommunity.com/u/dontpanicburns)\
**Post date:** [February 17, 2023, 12:15pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/54 "2023-02-17T12:15:27Z")

</div>

where is everyone tracking node counts and what stats are we targeting for ‘good’?

I see 7564 nodes on the [blockchair](https://blockchair.com/zcash/nodes) site this morning. The 24hr tx count is [4255](https://bitinfocharts.com/zcash/) and 4710 github stars. This has been reasonably average for the last few months.

Ethereum mainnet has between [4866](https://ethernodes.org/) and [12700](https://etherscan.io/nodetracker) nodes depending on how you count

btc has [15248](https://bitnodes.io/) and had a 24hr tx count of [316,268](https://bitinfocharts.com/bitcoin/)

my btc full node is ~450gb, my eth node is around 650 gb with pruning, and my zec node is 267gb

Eth would be around 12 tb with no pruning. 10+ tb of spam nfts, tokens, and other bs

This is a bear market. Only true fans, businesses, and experts are running nodes. Nodes will come with price appreciation and adoption.

Zec node count is much higher than I would have guessed from this thread. Especially considering we push a majority of users to light wallets that all default to lightwalletd or zecwallet end points.

Edit:  
Follow-up question: Is there an efficient way to know how many notes have been generated per pool?

iirc the tree can have at most 2^32 leaves and ‘spam’ could be be defined somehow related to this

---

<div class="post-metadata">

**Author:** ![Autotunafish](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/autotunafish/32/7827_2.png) [@Autotunafish](https://forum.zcashcommunity.com/u/Autotunafish)\
**Post date:** [February 17, 2023, 2:20pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/55 "2023-02-17T14:20:01Z")

</div>

You need to exclude anything labeled magicbean v6 and certainly anything below v5 (it doesnt count zebra nodes). The actual count is closer to 200

---

<div class="post-metadata">

**Author:** ![noamchom](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/noamchom/32/20269_2.png) [@noamchom](https://forum.zcashcommunity.com/u/noamchom)\
**Post date:** [February 17, 2023, 4:13pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/56 "2023-02-17T16:13:11Z")

</div>

200 Zcash full nodes is the global count?

---

<div class="post-metadata">

**Author:** ![Autotunafish](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/autotunafish/32/7827_2.png) [@Autotunafish](https://forum.zcashcommunity.com/u/Autotunafish)\
**Post date:** [February 17, 2023, 4:20pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/57 "2023-02-17T16:20:55Z")

</div>

Yes, 20characters

---

<div class="post-metadata">

**Author:** ![dontpanicburns](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/dontpanicburns/32/32565_2.png) [@dontpanicburns](https://forum.zcashcommunity.com/u/dontpanicburns)\
**Post date:** [February 17, 2023, 4:27pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/58 "2023-02-17T16:27:39Z")

</div>

200 is closer to what I would have guessed thh

Interesting, I went down the rabbit hole of magicbean v6 and flux.

They seem to be running the ~same software so it will have all the same limitations. Node running is incentivized in some sort of tiered model. They offer [vps pricing](https://docs.google.com/spreadsheets/d/1KJf9yI7RGl01ZgkWA8qVPQUwChEfe0JK2UGfubnq4Fw/edit#gid=0) for running a node from their website, It looks like it costs \<30 eur to run a node a month.

minimum requirements:

- 2 Cores
- 4 Threads
- 8 GB RAM
- 220 GB SSD/NVME
- 180 MB/s DWS
- 240 EPS Min. Requirements
- 25 Mb down/up speed

[flux blockchaininfo](https://home.runonflux.io/daemon/blockchain/getblockchaininfo)

---

<div class="post-metadata">

**Author:** ![Autotunafish](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/autotunafish/32/7827_2.png) [@Autotunafish](https://forum.zcashcommunity.com/u/Autotunafish)\
**Post date:** [February 17, 2023, 4:57pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/59 "2023-02-17T16:57:21Z")

</div>

Convenience is conformist utopian idealism premised on some other less-happy laborious thing. It can have the intoxicating effect of making other (counter-culture) options unthinkable. Be aware

---

<div class="post-metadata">

**Author:** ![dontpanicburns](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/dontpanicburns/32/32565_2.png) [@dontpanicburns](https://forum.zcashcommunity.com/u/dontpanicburns)\
**Post date:** [February 17, 2023, 5:43pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/60 "2023-02-17T17:43:27Z")

</div>

IDK, I’m 100% for it being as easy as possible for people to deploy and run nodes. The lightwalled docker-compose file is 🧑‍🍳🤌

If there was a Infura for zcash developers, I do not think that would be a bad thing

---

<div class="post-metadata">

**Author:** ![hanh](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/hanh/32/27853_2.png) [@hanh](https://forum.zcashcommunity.com/u/hanh)\
**Post date:** [February 17, 2023, 7:24pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/61 "2023-02-17T19:24:24Z")

</div>

There is an ongoing grant for something like that. It would great to have an update on its status.

---

<div class="post-metadata">

**Author:** ![dontpanicburns](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/dontpanicburns/32/32565_2.png) [@dontpanicburns](https://forum.zcashcommunity.com/u/dontpanicburns)\
**Post date:** [February 17, 2023, 7:31pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/62 "2023-02-17T19:31:00Z")

</div>

I think this is the grant: [ZF Grants - Zcash Blockchain Infrastructure](https://grants.zfnd.org/proposals/1795471954-zcash-blockchain-infrastructure)  
From what I can see, the last update to milestones was paid out in May of 2022

@decentralistdan may have more insight

---

<div class="post-metadata">

**Author:** ![hanh](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/hanh/32/27853_2.png) [@hanh](https://forum.zcashcommunity.com/u/hanh)\
**Post date:** [February 17, 2023, 8:22pm UTC](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126/63 "2023-02-17T20:22:16Z")

</div>

In my opinion, it is more important to decentralize Lightwalletd instances.

There aren’t any official public deployments. ZW and NH received grants to run their servers but I am not sure it qualifies as public.

But even if you count them, that is only 2.

[Previous page](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126.md?page=2)

[Next page](https://forum.zcashcommunity.com/t/zcash-blockchain-size-risks/43126.md?page=4)
