Help with recovering keys for old Zillet users

Web3Auth Community General
1

To be transparent, keys generated with that old SDK may no longer be recoverable due to architectural changes and long-standing deprecation.

maharshi A lot of users are currently unable to access their accounts. If there’s any way you could assist us in recovering these accounts, we’d greatly appreciate it.

We’re also in the process of migrating to a new version with updated keys managed through the dashboard, but it’s hard to find stuff a lot of links are broken. Is there any working example for Nuxt 3 using the CustomAuth SDK?

2

Here’s a summary of your request and the relevant details for the support team:

Issue Summary:
You are seeking help to recover keys/accounts for old Zillet users who are unable to access their wallets, possibly due to architectural changes and deprecation of the SDK previously used. You referenced a statement indicating that keys generated with the old SDK may no longer be recoverable.

Link to Forum Post:
Zillet Wallet Access - New

Current Context:

  • Many users are currently locked out of their accounts.
  • Zillet is migrating to a new Web3Auth version with keys managed via the dashboard.
  • You are requesting any possible assistance to recover the old accounts.

Missing Technical Details:
To assist further, the support team may need:

  • The name and version of the old SDK used for key generation (if you know it).
  • Any code snippets or configuration details from the legacy integration.
  • Information on the authentication method and verifier (if custom authentication was used).
  • If you have any logs, error messages, or screenshots from affected users, please share them.

Guidance & Documentation:

Next Steps:

  • If you have any details about the legacy SDK or authentication configuration, please provide them here. This will help the support team assess if any recovery options are available.
  • If you have user addresses or identifiers for affected accounts, please gather them (do not post sensitive info publicly).

Note:
Due to architectural changes and deprecation, it may not be possible to recover keys generated with the old SDK, but the support team will review your case and advise on any possible solutions or workarounds.

Thank you for providing context and for your patience as the team investigates this issue. If you have any additional technical details or user reports, please add them to this thread.

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

1 Like
3

We’re working on a Nuxt 3 app and have managed to integrate the @toruslabs/customauth SDK. Here’s what we’ve done so far:

torus.client.js

import { defineNuxtPlugin } from '#app';
import { CustomAuth } from '@toruslabs/customauth';

export default defineNuxtPlugin((nuxtApp) => {
  const torus = new CustomAuth({
    baseUrl: window.location.origin + '/serviceworker',
    network: 'sapphire_devnet', // using devnet for testing
    enableLogging: true,
    web3AuthClientId: '<CLIENT_ID>', // from Web3Auth Dashboard
  });

  torus.init();
  nuxtApp.provide('torus', torus);
});

in one of component

const loginDetails = await $torus.triggerLogin({
  clientId: '<GOOGLE_CLIENT_ID>',
  authConnection: 'google',
  authConnectionId: 'google-zillet',
});

console.log(loginDetails);

However, I’m getting the following error after calling triggerLogin:

Error when cleaning token verifier: google-zillet not found for account id: 5Grw....tQY

If i change network to ‘devnet’ i get following error

Error occurred while verifying params aud: <GOOGLE_CLIENT_ID> or azp: <GOOGLE_CLIENT_ID_2> is not matching clientID: <GOOGLE_CLIENT_ID_2>

I tried testing with the keys I found in this example, with these everything is working as intended CustomAuth/examples/vue-app at master · torusresearch/CustomAuth · GitHub

2 Likes
5

@maharshi @automotomir64 @alexander.akulich

6

I can only create Sapphire mainnet and testnet client keys on the dashboard, but I want to make requests to the old mainnet. That way, I can help users recover their keys.

7

Do you have the olde client id and the network?
Can you just share the network it belongs to?

8

find the details in this old implementation

 const torusdirectsdk = new TorusSdk({
          baseUrl:
            process.env.TORUS_SW_URL ||
            window.location.origin + '/serviceworker'
        });

const loginDetails = await torusdirectsdk.triggerLogin({
          typeOfLogin: 'google',
          verifier: 'google-zillet',
          clientId:
            '<google_client_id>'
        });
9

Hey @ZilletDev
This is the Google client id. There should be a Torus/Web3Auth client id.

10

old code doesn’t have any client id, I also checked the requests and one of the request looks like this which is not resolving


curl 'https://torus.zilliqa.network/jrpc' \
  --data-raw '{"jsonrpc":"2.0","method":"VerifierLookupRequest","id":10,"params":{"verifier":"google-zillet","verifier_id":"testuser@zillet.io"}}'

and throwing this error

node results do not match at first lookup {}, {}

you can check it out here https://v1.zillet.io/

11

@ZilletDev Please create a new project on the dashboard. You’ll get a client id for that project, please share that with me. We’ll internally link the verifier you’re using(google-zillet) to the project id you’ll be giving to me. So that the addresses for your users wouldn’t change.

12

Hey, here’s the client Id i received for the sapphire_mainnet

BHCb7w74ne6HCnDFqpf-t_4t1VpVkDcpVPMSII1naFp8vrUdgIne5yHUVj9oamrEWZOYc99yNCjo9XHxI7yPibE
13

I have asked the engg team to attach your old verifier to the new client id, I’ll update you of the timelines.

2 Likes
14

Any updates regarding this?

15

Hey @ZilletDev,
Thanks for your patience. We’re trying to find out the right verifier to link to your project. But till them please be informed that we have changed the web3auth environment to legacy mainnet. As the verifier was probably of the erstwhile mainnet web3auth environment, which we have renamed as legacy mainnet now.

16

Hey @ZilletDev
i have an update for you.
Please use the client id you’ve created i.e. BHCb7w74ne6HCnDFqpf-t_4t1VpVkDcpVPMSII1naFp8vrUdgIne5yHUVj9oamrEWZOYc99yNCjo9XHxI7yPibE

The code you’ve written is pretty much correct but just switch the web3auth network to legacy_mainnet
And use the verifier you had (google-zillet I believe).
Your integration should work as intended.
let me know if you have any queries or if this doesn’t work.

17

it throws an error saying “Invalid network”

torus.client.js

import { CustomAuth } from '@toruslabs/customauth';

export default defineNuxtPlugin((nuxtApp) => {
  // 1️⃣ configure your CustomAuth options
  // get these values from your Torus dashboard:
  const torus = new CustomAuth({
    baseUrl: window.location.origin + '/serviceworker',
    network: 'legacy_mainnet', // details for test net
    enableLogging: true,
    web3AuthClientId:
      'BHCb7w74ne6HCnDFqpf-t_4t1VpVkDcpVPMSII1naFp8vrUdgIne5yHUVj9oamrEWZOYc99yNCjo9XHxI7yPibE', // get Client ID from Web3Auth Dashboard
  });
  // 2️⃣ instantiate
  torus.init();
  // 3️⃣ expose it globally as `$torus`
  nuxtApp.provide('torus', torus);
});
18

Hey @ZilletDev
Can you just pass “mainnet” ?
CustomAuth was released long back, so the legacy was appended for all the newer SDKs.

1 Like
19

Hey, It worked. thanks for your help

20

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.