What is Chain Namespace?
It signifies the type of chain you want to initialize web3auth with.
Eip155 option is for EVM compatible chain (Ethereum, Polygon etc.)
Much awaited plugin thank you! I’ve just bought it and am setting it up, taking guidance from the demo workflows.
However when my “Login Web3Auth A” event is triggered, I get the correct popup but the blue circle turns and never loads the login buttons. I’ve alr created my clientID in web3auth, and added my project url to the whitelist. Chain ID, RPC url, chain namespace values are default (Ethereum mainnet infura).
Could you help me here pls? What should I do with my clientID, where should I paste it? Is my URL formatted incorrectly in the whitelist?
Another thing - the demo site Torus login doesn’t seem to work; when I click the Torus button it goes to a never ending blue circle again. Could you have a look at this please?
Hi, any update on the non-working Torus button? I’ve observed this consistently across different computers (all Chrome). Are you seeing this as well on your end too? Thanks
Thanks ezdev. Another observation I’ve discovered if you could look into as well: a Web3Auth element in the page body (index), doesn’t seem to access the same connection instance of a Web3Auth element created a resusable element (eg. header).
This is unlike your “Metamask Login” plugin, in which an element created in index can access the connection status of an element created in the header. You can easily output the connected wallet’s address in the body, using the connected instance in the header.
Am I doing something wrong? What’s the correct way to display a connected user’s name in the page body, if I am using the Web3Auth element in the header?
Ah I see…hmm. Using only 1 element in the header though, the connection instance can’t be accessed in the page body. Is there another recommended way to use this plugin? Thanks for your guidance.
If your issue is accessing the data (wallet address, email, or is connected status), save them in separate custom states of the header element, then they will be accessible from anywhere on other pages.
hi, any luck debugging this? I just tried your demo page , the turning blue circle still appears but there seems to be a Torus login window behind it now. Unfortunately it doesn’t progress past this point and clicking the window behind doesn’t bring it forward
Hello,
Just before buying I wanted to make sure of a couple of things your app can do.
I want to on oard my users via your plugin.
If they never used web3auth before, will it create them an address for Polygon and ETH automatically so that they can sign transactions (after having deposited some funds lf course) ?
If so, are those addresses and transaction signing funxtions available in the plugin ?
Thanks a lot !
Hello,
firstly, you can try it by yourself and see what happens on the demo page, link is in the description.
The user can select one of his web3 wallet to connect with, if he doesn’t have one, he can connect via social network, in this case, a web3 wallet will be created automatically and it will be connected automatically with the selected social network that user used. And he will be able to sign messages as usual.
Thanks for your answer. So that means that for a user that logins via the plugin using Google Auth for example, they will be able to sign transactions and get back their wallet address on Polygon, directly with your plugin ?
The demo only shows me my email address and name, but not anything related to a web3 address, hence my questions
By going into the plugin dashboard, I see that the Web3auth connected wallet address seems available, you mean that this address will be populated with this created address ?
EDIT 3 : I see that you made some changes, and I see my connected wallet on the demo page !
Thanks again, your help is very precious
Web3Auth
