# \[Archive\] Which option to go with? tKey (self host SDK) or custom verifier?

**URL:** <https://builder.metamask.io/t/archive-which-option-to-go-with-tkey-self-host-sdk-or-custom-verifier/2221>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [January 4, 2023, 2:07pm UTC](https://builder.metamask.io/t/archive-which-option-to-go-with-tkey-self-host-sdk-or-custom-verifier/2221 "2023-01-04T14:07:45Z")\
**Posts on this page:** 2\
**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:** [January 4, 2023, 2:07pm UTC](https://builder.metamask.io/t/archive-which-option-to-go-with-tkey-self-host-sdk-or-custom-verifier/2221/1 "2023-01-04T14:07:45Z")

</div>

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

* * *

My objective is to be able to create the same wallet/key for a user regardless of whether the user signs in with her Google account or Twitter account.  
I read that an aggregate verifier is needed ([https://web3auth.io/docs/custom-authentication/verifiers#aggregate-verifiers](https://web3auth.io/docs/custom-authentication/verifiers#aggregate-verifiers)).  
At the same time, the self-host option ([https://web3auth.io/docs/sdk/self-host/](https://web3auth.io/docs/sdk/self-host/)) seemingly can achieve this objective as well.  
Are these two options both viable to achieve this goal?

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

---

<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:** [January 5, 2023, 7:17am UTC](https://builder.metamask.io/t/archive-which-option-to-go-with-tkey-self-host-sdk-or-custom-verifier/2221/2 "2023-01-05T07:17:37Z")

</div>

Hey [@auracheeze](https://github.com/auracheeze)

If your objective is to create the same wallet/key for a user regardless of login provider, provided they both use the same email, or there must be a unique identifier between the JWT returned from each provider. Let's say `email`.

Then, you can aggregate the verifiers and get the same key back.

The question here is whether to choose aggregate verifiers or self-host. So, the aggregate verifier is a feature and can be available to both the Self-Host SDK and our Plug n Play SDKs.

  
   
 Originally posted by: [shahbaz17](https://github.com/shahbaz17)