# Zingo 2.0, Sync With Max Zing **URL:** \ **Category:** Zcash Apps\ **Created:** [July 14, 2025, 7:11pm UTC](https://forum.zcashcommunity.com/t/zingo-2-0-sync-with-max-zing/51652 "2025-07-14T19:11:59Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![frankbraun](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/frankbraun/32/45665_2.png) [@frankbraun](https://forum.zcashcommunity.com/u/frankbraun)\ **Post date:** [July 17, 2025, 10:33pm UTC](https://forum.zcashcommunity.com/t/zingo-2-0-sync-with-max-zing/51652/8 "2025-07-17T22:33:20Z")
> [@zancas](#): > > To minimize the danger from leaky taddress use, Zingo2.0 offers a convenient taddress generation feature, so that each use of a taddress can produce a unique taddress that’s uncorrelated to any other revelations. Interesting design choice, I like it. I just tested it and if you don’t mind, here are some additional suggestions, based on my understanding that you want to give the most authority to the user and let him make explicit decisions, rather than having things done automatically for him: - If a t-address has already been used I would show a warning on the screen where it is shown and advise the user to generate a new one, to prevent linking two transparent transactions together by reusing the t-address. - If a user has received funds on two (or more) _different_ t-addresses shielding them will link them together. If you want to give the user explicit choice you could warn him about the the linking and offer him a choice to just shield one of them (to prevent linking). - It might also be a good idea to show the amount of time that has elapsed since the last shielding operation (to make timing attacks harder). - Maybe you can even show the number of transactions that happened _on chain_ since the last shielding transaction, if you have an easy way to query that from the backend. To give the user a better estimation if enough time has elapsed since the last shielding transaction to make timing attacks harder. - Funds received in multiple transactions on the same t-address can and should always be shielded together. They are linked anyway, so nothing can be gained anymore by shielding them separately. In this post I describe a similar possible mechanism for Zashi, but with a UX where most decisions are made automatically for the user: > [@Why does Zashi only allow 1 Transparent address?](https://forum.zcashcommunity.com/t/why-does-zashi-only-allow-1-transparent-address/51538/7): > > I ordered one just so I can use it to store shielded Zcash on a hardware wallet. Having the ability to securely store shielded Zcash “at rest” is crucial for privacy in my opinion and you don’t want to store larger amounts on Zashi itself (because of the inherent security issues of mobile phones, not the software itself). And privacy is the biggest differentiator of Zcash, so that’s a very important feature to have. Would it be great to have support for shielded addresses in more widely used h… --- _[View the full topic](https://forum.zcashcommunity.com/t/zingo-2-0-sync-with-max-zing/51652)._