You unfortunately deprecated the testnet.
So I set up new Custom verifiers for dev environments.
But It does not work.
Error is below, But new custom verifier is certainly exists on mainnet and I use correct client_id for mainnet.
What happend?
Error: Could not get result from torus nodes
Verifier not supported. Check if you:
1. Are on the right network (Torus testnet/mainnet)
2. Have setup a verifier on dashboard.web3auth.io?
@m-ito Thanks for reaching out.
Your issue has been forwarded to our team and we will get back with updates soon.
Verifier that is already exists with same client_id works well on local env.
But this verifier can not use dev environment due to whitelist URL config.
It’s a shitty specification that we can’t update the whitelist URL after deploying.
Can you share your implementation code? I think the reason here might be related to wrong web3authNetwork parameter in the web3auth constructor code.
Also you can add or remove any whitelist url at any point of time. It is all done using client id and has no relation to verifiers. Just make sure the client id and verifier are on the same network for it to work properly.
Your advise is correct, thanks.
web3authNetwork was ‘testnet’ although I try to connect to mainnet varifier.
I fixed it to ‘mainnet’, then login functions work well.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.