Zillet wallet access new

[automotomir64]

Hello.

Can you help me with zillet wallet?
I registered in zillet.io via Google Auth, provided by you. And I can’t connect to my wallet for a half of a year. Zillet support always saying: the problem is on Web3Auth side.
I have a lot of money in this wallet. Also there are s lot of users with the same problem.
Please, help us to resolve this problem!

[w3abot]

Thank you for reaching out and sharing your experience, Oleg. I understand how concerning it must be to not have access to your Zillet wallet, especially with significant funds involved.

From your message, here’s what I’ve gathered:

• Platform: Zillet.io
• Login Method: Google Auth (via Web3Auth)
• Issue: Unable to access wallet for over 6 months
• Zillet support says the issue is on Web3Auth’s side
• Multiple users are affected

To help our support team investigate further, could you please provide:

1. The exact error message or behavior you see when trying to log in (e.g., does the login fail, or do you get stuck at a certain step?).
2. Any screenshots of the error or browser console messages, if possible.
3. The browser and device you are using.

This information will help us pinpoint the issue more quickly. In the meantime, if you haven’t already, please try clearing your browser cache or using a different browser to see if the issue persists.

Rest assured, we take situations like this seriously and will do our best to assist you. Thank you for your patience!

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

[automotomir64]

[maharshi]

Hey @automotomir64,
Thanks for bringing this up. I just tried logging in myself to create a new Zillet wallet and ran into the same issue.
After a bit of digging, I found that Zillet is using a very old, deprecated version of Web3Auth that has long been sunset. I’d strongly recommend they avoid spreading misinformation about Web3Auth’s reliability when the real issue is their lack of platform maintenance and refusal to upgrade to supported SDKs.
If anyone from the Zillet team is reading this, we’re happy to help you migrate to the latest stable Web3Auth SDKs. Just reach out and we’ll get you set up quickly.
In the meantime, @automotomir64, I’d personally advise avoiding platforms that don’t prioritize users’ financial safety or keep their authentication infrastructure up to date.

[alexander.akulich]

I’ve copied your answer to Zillet Community Chat in Telegram Telegram: View @zillet_wallet

Here is the answer of main developer of Zillet

Hey, I’ve asked for help multiple times in the discord dev chat if you have paid attention really, starting back in December last year, but no one really seems to be responding and the few answers I’ve received have been vague and then ignored by the team. The integration was done by the Torus team last time, and I have no way of knowing how they generated the application specific keys or how I should upgrade it. I tried following the docs mentioned in the Discord chat, but they didn’t lead anywhere. I really appreciate you reaching out to help, can we connect directly to work toward a resolution?

[maharshi]

Hey @alexander.akulich, appreciate you sharing the Zillet developer’s message.

Just to clarify a few things:

1. If they’ve been reaching out for help, it hasn’t been on any official Web3Auth support channel, definitely not here on the Web3Auth Community or through our structured support flows. We’d encourage them to bring the conversation here where it can be tracked and resolved transparently.

2. We’ve published clear, step-by-step migration guides, and multiple teams have successfully moved from deprecated SDKs to the latest versions with minimal friction. Many of them were on similarly outdated stacks. The difference? Intent. Teams that truly prioritize user access and security have taken the steps, and succeeded.

We’re more than happy to help Zillet upgrade and resolve this issue. But they need to show up in the right channels, and with the willingness to fix what’s clearly within their control.

[ZilletDev]

Hey! I’m Zillet dev and would really appreciate it if you could help connect me with someone who can help resolve the issue. Last time the integration done by YZhenY in this PR Feat/integrate torus by YZhenY · Pull Request #49 · zillet/zillet · GitHub

[maharshi]

Hey @ZilletDev, appreciate you joining the conversation.

We looked at the PR you referenced, yes, the integration was originally done by Zhen back in the Torus days, using what is now known as the CustomAuth SDK (previously called direct-web-sdk). That SDK has been deprecated for several years now, and unfortunately, continued usage of it has led to exactly the kind of issues you’re now facing.

To be transparent, keys generated with that old SDK may no longer be recoverable due to architectural changes and long-standing deprecation. We’ve consistently announced deprecation timelines and shutdown notices across all our official channels to give teams ample time to migrate.

We’ve seen other projects in similar situations successfully upgrade using our migration guides in our docs, but that transition requires technical intent and willingness. We’re glad you’ve reached out now.

Here’s how we can move forward:

1. Create a new project on the sapphire_devnet environment to begin testing with our latest SDKs.
2. Share your current implementation status, and we’ll help guide you through setting up a modern integration.

Let’s work together to resolve this, but do note, this is a dapp-side integration issue, not an end-user support scenario (Please take note, @automotomir64, @alexander.akulich).

We encourage teams to keep their auth stack current, especially when users’ financial access is at stake.