With all the cool stuff that’s being added to Zashi, I’m kind of blown away that we still can’t generate new T-addresses. Often times receiving to a T-address is unavoidable, why are we forced to reuse the same T-address over and over again in Zashi?
I really appreciate all that amazing work that’s been going into Zashi, but this has me dumbfounded. It seems so fundamental.
They announced that this will be fixed soon. Related: Why does zashi re-use the same receiving t-address? - #21 by pjv
Did you link to the correct post? I don’t see any developer mention that.
It was a bit further up in that linked topic here:
A couple posts down from that one he indicated Q2 as the timeline for it. About 9 days left in Q2 and while all kinds of new, hyper-niche, featurific additions have landed in zashi in the mean time, this most basic, most fundamental to actual, usable, pragmatic privacy, this simple piece of elemental basic crypto-currency plumbing that has tons of examples of open source prior art in over a decade of development of bitcoin and other crypto wallets all over the place, has inexplicably not managed to arrive in zashi. It’s honestly unbelievable.
What did we add that is “hyper niche?”
For taddr rotation, we need to solve a security issue that involves core, and core has been focused on 6.1 and Zallet.
If user receives funds to multiple taddrs and then shields them all at the same time, it reveals information to potential attackers. They will have some ability to determine that they are from the same wallet. For example, if the attacker sends funds to a taddr, they can then monitor when those funds are shielded and gain information from the other balances that were shielded simultaneously. There is some discussion about leakage minimization by spreading the shielding out over time, which could be a usability issue as the user cannot send funds from a taddr in Zashi.
How many people on planet earth own a keystone device?