# \[Archive\] Different Wallets: same clientid and same verifier

**URL:** https://builder.metamask.io/t/archive-different-wallets-same-clientid-and-same-verifier/2425
**Category:** Embedded Wallets (Web3Auth)
**Created:** [September 7, 2022, 8:58am UTC](https://builder.metamask.io/t/archive-different-wallets-same-clientid-and-same-verifier/2425 "2022-09-07T08:58:46Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![githubdiscussions](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@githubdiscussions](https://builder.metamask.io/u/githubdiscussions)
#### Post date: [September 7, 2022, 8:58am UTC](https://builder.metamask.io/t/archive-different-wallets-same-clientid-and-same-verifier/2425/1 "2022-09-07T08:58:46Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **githubdiscussions** on 9/7/2022.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

A user got a different wallet despite having same clientId, same aggregateVerifier (tkey-auth0-email-passwordless), same verifier (torus) and same verifierId.  
He logged in on 6/13/22 and 8/02/22.

The app has been running in production for a few months and the problem has only occurred with one account so far.

  
   
 Originally posted by: [andrebruch](https://github.com/andrebruch)  
   
 Check the discussion at: [https://github.com/orgs/Web3Auth/discussions/566](https://github.com/orgs/Web3Auth/discussions/566)