I would like to know if I can use the service by using Wagmi+pnp.
if I use web3auth, I can use services.
but if I connect with wallet such as metamask, can I use services?
do you know what I meant?
I would like to know if I can use the service by using Wagmi+pnp.
if I use web3auth, I can use services.
but if I connect with wallet such as metamask, can I use services?
do you know what I meant?
You can use all of that options to connect to your Dapp, but Web3auth is not in the list.
totsr wallet is web3auth, I changed logo.
Yes, but you need to share some code with us explaining what happens when you click on that text.
hi @devcrypto389,
Sorry, I can’t find any error.
Would you like to share with me a github working project ?
Also if you would like to have a priority support you can schedule a call with our team → Calendly - Web3Auth
ok. what’s your github username?
I can invite your to our repo.
I just sent you a private message with my GitHub username.
just invited you.
plz check and let me know about the issues.
You have some issues in the package.json file and I am unable to execute it. Please refer to our example and consider doing console.log
to see if you are getting data fom userInfo
and isConnected
as well.
const {
initModal,
web3Auth,
userInfo,
isConnected
} = useWeb3Auth();
totsr-front git:(main) npm i
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: digi_presale@0.1.0
npm ERR! Found: near-api-js@4.0.2
npm ERR! node_modules/near-api-js
npm ERR! near-api-js@"^4.0.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer near-api-js@"^3.0.4" from @idos-network/idos-sdk@0.2.16
npm ERR! node_modules/@idos-network/idos-sdk
npm ERR! @idos-network/idos-sdk@"^0.2.16" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
it’s because of the node version.
plz try this for installing module…
npm i --legacy-peer-deps
@TomTom
Ok…the issue is that your are using Shapire_mainnet for a product requiring Scale Plan. Please use Shapire_devnet for testing purposes.