Walletconnect - blocked by CORS policy

[kim]

Hi, hope someone can help. I’ve read several post regarding this issue or similar to these. Most of them seems that fixed by magic. I’ve been facing this issue for 3 days and still not able to get over it.

I have no issue to connect via metamask. these errors only happen on walletconnect. My observation is no issue to authenticate/connect via walletconnect (no error). Errors will start popup out on the console after connected for 3-5 seconds and will continue get the several new error entries per seconds.

I tried pasting the https://speedy-nodes-nyc.moralis.io/WalletConnect/bsc/mainnet%20net on browser, then I’m getting " You are being rate limited" by cloudflare.

I tried restarted moralis server. I deleted the server and re-create. can’t resolve.
Can someone help?

[cryptokid]

There is a rate limit per IP on how many requests can be made to that RPC url specific to wallet connect that is a public RPC url. That could be a reason why you could get that error in testing if you test it few times.

[kim]

thanks for the info.
any idea what is eth_blockNumber? it keeps generating requests to moralis server

[cryptokid]

it looks like it tries to get the last block number, it could do that in order to know when it passed a number of block in order to check if the transaction made it to the chain

[kim]

anyone can help to solve this?

[cryptokid]

you say that it makes continuous requests to that wallet connect RCP endpoint?

it will get rate limited if it happens to make a lot requests

[kim]

yeah… i understand the needs of rate limit at moralis firewall side.
But I don’t understand why this only happens when connect via walletconnect. No such issue with browser extension metamask. I tried tokenpocket browser no issue as well

[cryptokid]

when using metamask extension, a different RPC url will be used, the one that is added in metamask configuration, and also, metamask may not make the same number of requests

I don’t know now why walletconnect would make so many requests to that RPC url, you don’t even need to connect to the RPC in order to authenticate, only when you want to make a transaction

[Martinpriv]

Hey Kim…was having the same issue. Took me the whole day to get a solution.
Not the best but its working…

There is a problem with the Wallet_connect web3 provider.
https://github.com/WalletConnect/walletconnect-monorepo/releases/download/1.7.8/web3-provider.min.js

async _updateLatestBlock() {
	const t = await this._fetchLatestBlock();
	this._newPotentialLatest(t)
}

I just saved the file locally and edited this function with a little wait time. The function was called to often so the Request Rate Limit error was caused.

async _updateLatestBlock() {
        console.log("Updating latest Block");
        const waitFor = delay => new Promise(resolve => setTimeout(resolve, delay));
        await waitFor(1500);
	const t = await this._fetchLatestBlock();
	this._newPotentialLatest(t)
}

Not the best solution…but it works.

[kim]

I realised walletconnect will start this RPC request as soon as I press “Connect” on metamask and will continue do so until I disconnect (localstorage.clear and moralis.user.logout).
My understanding is that walletconnect try query the latest update constantly from the node (moralis in this case) while moralis’s firewall (cloudflare) configured to limit the request.

[kim]

thanks for the workaround. I tried and I even increased it to 60000. 0 Errors! but not usable. Update is too much delay.

I’m now using your workaround and set the delay to 5000 and keep my finger crossed!!

[osborn1900]

did this work for you ? i have the same issue

[osborn1900]

what directory did you save this file to? how do i edit it in the npm package.

[osborn1900]

@Martinpriv

console.log("Updating latest Block");
        const waitFor = delay => new Promise(resolve => setTimeout(resolve, delay));
        await waitFor(1500);

thanks for this solution, but does that mean if i run npm i on a production version, i wont be able to see the changes?

[alex]

You could use your own version of the WalletConnect package in your project or patch the change (in node_modules) with something like patch-package.

[osborn1900]

I ended up using a custom connector and lived happily ever after!

[JUMPER]

Can you please explain, what the custom connector?

[cryptokid]

A custom connector could be this:
https://v1docs.moralis.io/moralis-dapp/users/web3-login/custom-auth-any-eip1193-provider

MoralisWeb3/Moralis-JS-SDK-v1/blob/main/src/Web3Connector/WalletConnectWeb3Connector.js

[DeathStar]

@Martinpriv

const waitFor = delay => new Promise(resolve => setTimeout(resolve, delay));
        await waitFor(1500);

Hi @osborn1900, can you share code snippet how you implemented this custom one?
I am using metamask for browser and for mobiles using wallet connect in my React and Next JS dApp.

configuration : moralis-v1 sdk, react-moralis, walletConnect

[DeathStar]

Hey, I downloaded this file and made the changes, but where do I need to keep this file. I am using @walletconnect/web3-provider package. I am stuck in this @Martinpriv @kim @osborn1900