# Zecwallet Lite Security Updates and Review **URL:** \ **Category:** Applications\ **Created:** [January 6, 2021, 9:09pm UTC](https://forum.zcashcommunity.com/t/zecwallet-lite-security-updates-and-review/38169 "2021-01-06T21:09:41Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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:** [January 10, 2021, 1:32am UTC](https://forum.zcashcommunity.com/t/zecwallet-lite-security-updates-and-review/38169/3 "2021-01-10T01:32:18Z")
> [@adityapk00](#): > > Cache the entire Compact blockchain in memory, trading off higher resources for faster sync speed. Combined with multi-threaded syncing support on the client side, this significantly improved sync speed, which was the biggest complaint lite wallet users had. Would it be helpful to move your performance improvements in zecwallet-light-cli and lightwalletd with the ECC’s counterparts? What would be the advantages and disadvantages of this? Thanks for all your work for the ecosystem, Aditya. As one of the community projects using the Zecwallet SDK and your lightwalletd infrastructure I’m really grateful for your work! Also, to be super explicit about a potential conflict as a ZOMG member—which I don’t think is a conflict, but could be—my project Zbay is a user of Zecwallet SDK, so I have an interest in it getting improved, security audited, etc. I think this mostly _isn’t_ a conflict because many people in the ecosystem share this interest, and because I explicitly ran on a platform of focusing on user facing apps and representing an app developer’s perspective (see [my announcement](https://forum.zcashcommunity.com/t/holmes-wilson-for-mgrc/37034) 🙂 ). But all of this is uncharted territory so I wanted to note it here. --- _[View the full topic](https://forum.zcashcommunity.com/t/zecwallet-lite-security-updates-and-review/38169)._