# Static T-Address

**URL:** <https://forum.zcashcommunity.com/t/static-t-address/52295>\
**Category:** Zodl\
**Created:** [October 1, 2025, 12:41pm UTC](https://forum.zcashcommunity.com/t/static-t-address/52295 "2025-10-01T12:41:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kranzj](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/kranzj/32/27439_2.png) [@kranzj](https://forum.zcashcommunity.com/u/kranzj)\
**Post date:** [October 1, 2025, 12:41pm UTC](https://forum.zcashcommunity.com/t/static-t-address/52295/1 "2025-10-01T12:41:04Z")

</div>

Hi everyone,

it seems like the T-address in Zashi is static. I came across this as part of noticing that CrossPay currently basically removes privacy by sending back the change to same T-address that was used for topping up; Josh already said that this is going to be fixed soon. My question here is - is generating new T addresses (beyond CrossPay) a planned feature? I think reusing the same address across different payment sources (exchanges, wallets, …) is a massive privacy issue, but also seems easy to fix from a technical point of view.

I understand that using the private pool (u address) is the better choice, but the reality is that it is often not possible.

Thank you!

---

<div class="post-metadata">

**Author:** ![tloriato](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/tloriato/32/33218_2.png) [@tloriato](https://forum.zcashcommunity.com/u/tloriato)\
**Post date:** [October 1, 2025, 3:23pm UTC](https://forum.zcashcommunity.com/t/static-t-address/52295/2 "2025-10-01T15:23:46Z")

</div>

I don’t remember where I read - but yes, it’s planned (I think it was a message from Josh)

---

<div class="post-metadata">

**Author:** ![joshs](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/joshs/32/13631_2.png) [@joshs](https://forum.zcashcommunity.com/u/joshs)\
**Post date:** [October 1, 2025, 4:41pm UTC](https://forum.zcashcommunity.com/t/static-t-address/52295/3 "2025-10-01T16:41:20Z")

</div>

Yes, we are adding t-address rotation.
