# 2 Grin++ wallets showing same address

**URL:** <https://forum.grin.mw/t/2-grin-wallets-showing-same-address/10517>\
**Category:** Tech Support\
**Created:** [May 15, 2023, 10:30pm UTC](https://forum.grin.mw/t/2-grin-wallets-showing-same-address/10517 "2023-05-15T22:30:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Anynomous](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/anynomous/32/2928_2.png) [@Anynomous](https://forum.grin.mw/u/Anynomous)\
**Post date:** [May 16, 2023, 7:13am UTC](https://forum.grin.mw/t/2-grin-wallets-showing-same-address/10517/2 "2023-05-16T07:13:55Z")

</div>

> [@Skyr](#):
>
> nyone know why two different Grin++ wallets are showing the same address?

Because the grin tor address is basically a wrapped public key and as such derived from your wallet seed. If you use the same seed, the address will always be the same. If you like a new address (for example for better privacy), Grin++ has a generate new adress button.  
If you want to understand how the new address generation works, see this post:

> [@Vanitygen for Grin](https://forum.grin.mw/t/vanitygen-for-grin/10379/8):
>
> Here’s how I did it on Grin++ /\* \* From RFC-0010 (https://github.com/mimblewimble/grin-rfcs/blob/master/text/0010-online-transacting-via-tor.md): \* \* Although ed25519 is a different curve than used by the grin protocol, we can still use our HD wallets to \* generate deterministic ed25519 public keys (and therefore Grin addresses). For account m/0, addresses will be \* generated using keychain paths m/0/1/x, for account m/1, addresses will be generat…

---

_[View the full topic](https://forum.grin.mw/t/2-grin-wallets-showing-same-address/10517)._
