search

WalletConnect / walletconnect-monorepo

WalletConnect Monorepo
Apache License 2.0
1.35k stars 674 forks source link

Pairing fails with `verify/attestation/...` 404 #4639

Closed glitch-txs closed 2 months ago

glitch-txs commented 3 months ago

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](https://github.com/WalletConnect/web-examples/tree/main/advanced/wallets/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.
linear[bot] commented 3 months ago

CR-67 Pairing fails with `verify/attestation/...` 404

ganchoradkov commented 2 months ago

the attestation 404s because the dapp doesn't publish it thus its not available when the wallet tries to fetch.

404 occurs even before it triggers session-proposal

yes, this is expected as the attestation fetch is done before we emit session_propose.

To enable verify api, please go to cloud.walletconnect.com and update your settings