You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by asood123 February 5, 2024
Hi there -
I'm building a demo to allow an Account Abstraction Wallet to be used with a dapp via WalletConnect. I copied the code from react-wallet-v2.
When I call web3Wallet.pair({uri}) (with a valid wc... string from say Uniswap interface), it always fails with a 404 to verify/attestation/... call. Things I have tried:
verifying the domain by publishing on a vercel link but still same error. Is there a way to skip the verify call on localhost?
I thought maybe the dapp can require a verify call, so I even spun up a local dapp with a different walletconnect id and still same error.
404 occurs even before it triggers session-proposal (i.e. never reaches web3wallet.on('session_proposal', onSessionProposal)). I must be missing something obvious. Any pointers to debug why verify/attestation/ call is being placed (I thought it shouldn't be) and how to either skip it or avoid the 404 would be greatly appreciated 🙏 .
cc @thekidnamedkd, who's running into something similar.
The text was updated successfully, but these errors were encountered:
Discussed in https://github.com/orgs/WalletConnect/discussions/4204
Originally posted by asood123 February 5, 2024
Hi there -
I'm building a demo to allow an Account Abstraction Wallet to be used with a dapp via WalletConnect. I copied the code from react-wallet-v2.
When I call
web3Wallet.pair({uri})
(with a validwc...
string from say Uniswap interface), it always fails with a 404 toverify/attestation/...
call. Things I have tried:404 occurs even before it triggers
session-proposal
(i.e. never reachesweb3wallet.on('session_proposal', onSessionProposal)
). I must be missing something obvious. Any pointers to debug whyverify/attestation/
call is being placed (I thought it shouldn't be) and how to either skip it or avoid the 404 would be greatly appreciated 🙏 .cc @thekidnamedkd, who's running into something similar.
The text was updated successfully, but these errors were encountered: