# Zcash Node and lightwalletd Running PoC Proposal

**URL:** <https://forum.zcashcommunity.com/t/zcash-node-and-lightwalletd-running-poc-proposal/37934>\
**Category:** Applications\
**Created:** [December 10, 2020, 3:11pm UTC](https://forum.zcashcommunity.com/t/zcash-node-and-lightwalletd-running-poc-proposal/37934 "2020-12-10T15:11:46Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![holmesworcester](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/holmesworcester/32/15710_2.png) [@holmesworcester](https://forum.zcashcommunity.com/u/holmesworcester)\
**Post date:** [December 23, 2020, 3:37pm UTC](https://forum.zcashcommunity.com/t/zcash-node-and-lightwalletd-running-poc-proposal/37934/31 "2020-12-23T15:37:28Z")

</div>

> [@mika](#):
>
> We should avoid this kind of centralization - especially since this is critical infrastructure.  
> Provide the means such that it’s easy for people to run lightwalletd services. Ideally zcashd would provide lightwalletd services by default.

There are actually some serious disadvantages to this from a privacy and security standpoint. Light clients are still _very_ vulnerable to a malicious lightwalletd. You can see a rundown on these vulnerabilities here:

[https://zcash.readthedocs.io/en/latest/rtd\_pages/wallet\_threat\_model.html](https://zcash.readthedocs.io/en/latest/rtd_pages/wallet_threat_model.html)

Having lots of lightwalletd’s mitigates some of these issues, like the ability to analyze the transaction graph based on who is fetching memos, but as you add more lightwalletd’s, the chances of connecting to a malicious lightwalletd approach 1.

---

_[View the full topic](https://forum.zcashcommunity.com/t/zcash-node-and-lightwalletd-running-poc-proposal/37934)._