Ability to pregenerate wallet addresses for off-line users

We have a use case where we get the email addresses of our clients offline. We would like to generate these users’ wallet addresses so that when they log in to the system, web3auth actually generates the same wallet address. We need to regenerate it as we would like to assign these users some specific data in our DB, and we identify all the users using their wallet addresses.

Is there any SDK or CLI tool that we could use for a process like this?

Hi @mz7mz7mz7,

I hope you’re doing well. I wanted to suggest checking out our documentation on the pre-generated wallets feature. Here’s the link for easy access: Wallet Pregeneration | Documentation | Web3Auth. I believe it will provide you with a comprehensive overview and help you understand how this feature works.

Additionally, you have the option to test it out and see how it operates in practice, which might be really insightful.

If you have any more questions or need further clarification on this or any other topic, please don’t hesitate to get in touch. I’m here to assist in any way I can.

Looking forward to hearing from you and happy to help with any queries you might have!

Hi @TomTom ,

Based on your discussion with @mz7mz7mz7 and the link to the documentation you provided, I have a question to ask. For someone on the basic package, where can the value for verifier be found on the dashboard?

hi @ugwuhilary017

I hope you’re doing great! I wanted to point you toward our different plans to give you a better idea of what each offers: Web3Auth | Pricing - Personalised plans for everyone!. The wallet service is not supported in some of the plans.

If you’re considering upgrading your plan or have any questions about the features included in each, we’re more than happy to discuss this further. You can arrange a meeting with our team here: Web3Auth | Contact us. We’re here to help you find the best solution for your needs.

Thanks for reaching out, and I’m looking forward to assisting you further.

@TomTom Thanks for your response. From the link you shared in your response, does it mean that the only packages that can be used to pre-generate wallet addresses are the scale and enterprise package? How about the growth package?


hi @ugwuhilary017

Yes … you need to be at least in the Scale Plan.

Please contact our business team so they can orient you better.

Thanks

@TomTom So, we have used the pre-generated wallet option to generate addresses and compared it with the addresses that are generated using the web model. The generated wallets are different. Screenshots attached. Is there anyway we can make these generated wallets one and the same?


image

hi @ugwuhilary017
I hope you are doing well. Are you considering this warning ?

WARNING

This API only returns the Core Kit Key wallet addresses. To use the wallet addresses with the Web3Auth SDKs, you will need to either use the useCoreKitKey flag in our PnP SDKs or use any of our Core Kit SFA SDKs

@TomTom oh! I think I skipped that. However, going back to the documentation, I couldn’t figure out where to use the useCoreKitKey in the PnP SDKs. Do you mind point me to where I can use this key?

Hi @ugwuhilary017

yes, of course.

Please feel free to contact me again if you have any other problem

Hi @TomTom

Please when I set the useCoreKitKey option, I get the error as shown below

Kindly assist to enable us close out on this.

Thanks

Hey @ugwuhilary017,

I noticed that you are using the value web3auth for the verifier field while using the pregenerated wallets API. Could you please confirm if web3auth is indeed set as the verifier in your application? This error typically arises if the default verifiers are used by not specifying a custom verifier that you’ve created on the dashboard.

You can learn more about verifiers and how to create them here. This might help resolve the issue you’re facing.

Here is a screenshot of how I am initializing web3auth and the available properties on initialization.

@TomTom Also, here I am not calling the pregenerated wallet API. I am using the web PNP SDK and I am trying to confirm that this SDK generates the same address with the pregenerated wallets API.

Hello @ugwuhilary017,

I noticed you’re encountering an issue with the useCoreKitKey flag is enabled but coreKitKey is not available. error. This typically happens when no specific verifier is mentioned in your setup, causing the SDK to default to using pre-configured verifiers designed only for our PnP SDKs, which do not create a coreKitKey.

To resolve this, please familiarize yourself with the concept of verifiers as outlined in the documentation here. Additionally, you can see exactly how to implement a custom verifier in your application by checking out this example: Facebook No Modal Example.

Once you set a custom verifier, you should no longer see the error you’re currently experiencing. Please try this and let me know if it helps or if you need any more guidance!