# Social Verifier Migration **URL:** \ **Category:** Embedded Wallets (Web3Auth)\ **Created:** [September 8, 2025, 6:30am UTC](https://builder.metamask.io/t/social-verifier-migration/945 "2025-09-08T06:30:44Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![florian.bergmann](https://avatars.discourse-cdn.com/v4/letter/f/90db22/32.png) [@florian.bergmann](https://builder.metamask.io/u/florian.bergmann)\ **Post date:** [September 8, 2025, 6:30am UTC](https://builder.metamask.io/t/social-verifier-migration/945/1 "2025-09-08T06:30:44Z")
> **🏛 Content from Web3Auth Community** > > This topic was originally posted by **florian.bergmann** on 9/8/2025. > This content has been migrated from our previous community forum to preserve valuable discussions. * * * Hello, unfortunately a verifier got lost and I can’t add it as it seams to be already deployed. We run multiple “buckets” and it is just on one. As web3auth makes it really hard to reach support - how can I get into contact with someone manually resolving / connecting a deployed verifier with an app? ---
**Author:** ![w3abot](https://avatars.discourse-cdn.com/v4/letter/w/4da419/32.png) [@w3abot](https://builder.metamask.io/u/w3abot)\ **Post date:** [September 8, 2025, 6:33am UTC](https://builder.metamask.io/t/social-verifier-migration/945/2 "2025-09-08T06:33:57Z")
Hi Florian, thanks for reaching out and providing context! **Summary of Your Issue:** You’re running multiple “buckets” (projects/apps) and have a social verifier that appears to be “lost”—it’s already deployed, but you can’t add or connect it to your current app/bucket via the Web3Auth dashboard. You’re looking for a way to manually resolve this and connect the deployed verifier to your app, but haven’t found a support channel for this. * * * ### Details for Support Team - **SDK:** Web3Auth Plug n Play (PnP) - **Platform:** Web (exact framework not specified, but likely using the Modal SDK or No-Modal SDK) - **Issue:** Social verifier is already deployed (possibly under a different project/bucket), but cannot be linked or migrated to the current app/bucket. - **Migration Context:** User is aware of v9/v10 migration and dashboard-centric configuration, but this is a manual linking issue, not a code migration problem. * * * ### Next Steps / Suggestions This is a dashboard-level, account-specific issue that requires manual intervention from the Web3Auth team. Unfortunately, verifiers are unique and can only be linked to one project at a time; if a verifier is “stuck” in another bucket or project, only internal support can reassign or merge it. **What you can do:** - Please provide the following (if you haven’t already, or if support requests it): - The name of the verifier you’re trying to add - The app/bucket/project IDs involved (source and destination, if known) - Any error messages or screenshots from the dashboard when you attempt the action **Manual Support:** Web3Auth support typically handles these requests via their [contact form](https://web3auth.io/contact), or you can email [support@web3auth.io](mailto:support@web3auth.io) referencing this forum post for context. Please include the details above for faster resolution. **Reference:** - [Web3Auth Custom Authentication Migration Guide](https://web3auth.io/docs/migration-guides/custom-auth-v9-to-v10) - [Web3Auth Contact Page](https://web3auth.io/contact) * * * **You don’t need to provide code snippets or SDK logs for this issue, as it’s related to dashboard configuration and account management.** Let us know if you need help drafting your support request, or if you have additional details to share! > Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible. > Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. [Web3Auth Developer Office Hours](https://web3auth.io/community/t/web3auth-developer-office-hours/8777) ---
**Author:** ![maharshi](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/maharshi/32/1525_2.png) [@maharshi](https://builder.metamask.io/u/maharshi)\ **Post date:** [September 9, 2025, 7:06am UTC](https://builder.metamask.io/t/social-verifier-migration/945/3 "2025-09-09T07:06:33Z")
Hey @florian.bergmann You’ve reached the right place for support. I would love to know more details on this. Can you please explain what do you mean by your verifier getting lost? ---
**Author:** ![florian.bergmann](https://avatars.discourse-cdn.com/v4/letter/f/90db22/32.png) [@florian.bergmann](https://builder.metamask.io/u/florian.bergmann)\ **Post date:** [September 10, 2025, 9:57am UTC](https://builder.metamask.io/t/social-verifier-migration/945/4 "2025-09-10T09:57:02Z")
Hi, unfortunately I haven’t received any feedback on my support email for two days after the initial reply. As a client of over three years with an urgent matter, this is disappointing. By “getting lost” I mean: we’ve been using early versions of Web3Auth for years, but with the latest update, verifiers are now always loaded from the backend. The issue is that the “old verifier” we used during initialization in the JS code doesn’t appear to be linked to the correct account (since we manage multiple). This could represent a significant security concern, which might explain the rapid SDK updates. I’m happy to discuss the details further in the support email so we can resolve this properly. ---
**Author:** ![maharshi](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/maharshi/32/1525_2.png) [@maharshi](https://builder.metamask.io/u/maharshi)\ **Post date:** [September 10, 2025, 10:27am UTC](https://builder.metamask.io/t/social-verifier-migration/945/5 "2025-09-10T10:27:07Z")
> [@florian.bergmann](#): > > Hi, unfortunately I haven’t received any feedback on my support email for two days after the initial reply. We don’t provide email as a support channel for Basic, Growth, or Scale plans — our official support for those tiers is here on the [Web3Auth Community](https://web3auth.io/community). Enterprise customers get access to dedicated Slack/Telegram groups. > [@florian.bergmann](#): > > This could represent a significant security concern, which might explain the rapid SDK updates. Frequent SDK updates don’t automatically indicate security flaws. Like any evolving tech, Web3Auth continues to ship improvements and standardizations across platforms. Yes, vulnerabilities can surface — but fixing them quickly and moving forward is what ensures end-user safety. Staying on legacy versions is a bigger risk than updating. > [@florian.bergmann](#): > > As a client of over three years with an urgent matter, this is disappointing. By “getting lost” I mean: we’ve been using early versions of Web3Auth for years, but with the latest update, verifiers are now always loaded from the backend. The issue is that the “old verifier” we used during initialization in the JS code doesn’t appear to be linked to the correct account (since we manage multiple). To look into this further, please share: - The **verifier name** - The **client ID** you expect it to be linked to - The **Web3Auth network parameter** you’re using That info will help us pinpoint what’s happening and guide you to a resolution.