Wallet Connectivity Issue

[CharmOffnz]

The bug is a connectivity issue with browser wallets. I use Google Chrome v90.0.4430.212. I tried both MetaMask and Portis.

The issue happens when I reach Proof of Receive phase when trying to claim airdropped $GTC. I can check my browser wallet and see that the wallet is connected to the gitcoin site. I check the Chrome console and I see this error (screenshot attached). I'm operating on OS 10.15.5.

[Woo20]

Thank you for opening up this discussion, CharmzOffnz, as I’m experiencing the same issue. I’m using the latest Google Chrome and can’t get past the “proof of receive” stage. I once (out of dozens of tries) was able to connect my MetaMask and it was asking to input a delegate’s address (and another one which I can’t remember now), but it wouldn’t let me go further and soon went back to the original screen. I haven’t been able to connect since.

[nopslip]

Thanks for reporting the issue and sorry for the trouble. As we know that the token claim works with Chrome it seems likely there is some edge case here causing the problem.

If you are able to run additional tests here are somethings to try:

1. Are you running any adblocking extensions in your browser? If so, could you try to disable them and try the claim again?

2. Are you running any other security related extensions or plugins? VPN, antivirus, etc? If so, could you try disabling them and trying again?

3. Please confirm you're connected to the Ethereum Mainnet (not a testnet or Matic or something) - If you're on mainnet, consider trying switching to a different network and back to mainnet just to be 100% sure.

4. When you load the main Quadratic Lands page, please confirm that it's showing you do in fact have token available to claim.

5. Please try clearing browser cache and re-logging into browser wallet

If you're still seeing the error after these steps could click on the gitcoin.366... in your console log which will take you to the line in the file that error is coming from and paste the info here. (It's possible there is a new build file and it might be gitcoin.<something-else.).

Also, are you using the self delegate option or delegate to steward path?