Known ongoing incident with stcelo.xyz web app (Resolved)

[arthurgousset]

Hi all 👋

TLDR

• There is a known ongoing incident that affects stcelo.xyz users that connect using WalletConnect.
• This is related to the shutdown of WalletConnect v1 and migration to WalletConnect v2 today.

Live updates

Status: Resolved ✅

We will keep this Github Discussion updated, so wallet developers and the Celo community can follow along.

We apologise for the inconvenience and are working hard to bring back WalletConnect support for the stcelo.xyz app. Thank you for your patience! 🙏

[dckesler]

This appears to be an issue other people are struggling with in WalletConnect v2 right now. We're actively following this discussion now to see what the WalletConnect team suggests.

[nicolasbrugneaux]

Update Monday, July 3rd

Hello there, we are still hard at working trying to find a solution to this issue. The WalletConnect connecting issues seems widespread enough to impact users from a lot of chains and wallets. It seems however they're hard at work trying to fix these and we're in contact with them on their official discord and through the github discussion linked above.

While we're aware it doesn't help you at the time being, please know we're doing the best we can to get the ball rolling and get a fix ASAP. Furthermore, thanks to @jeanregisser we improved our WCv2 support with rainbowkit, and the StakedCelo v2 that should be released July 11th just happens to use rainbowkit. We will keep you inform of further progress.

Edit: additional reading on debugging with the WC team here

[nicolasbrugneaux]

Update Tuesday, July 4th (morning CET)

Hello there,

today's was marked by some good development, but still no definitive fix.

With the help of the WalletConnect team, we are debugging what seems to be a widespread issues with all wallets using wagmi under the hood, a PR was already merged and published but the source of our problems: the Failed to decrypt error still happens in production environments. We also have a direct thread with the WC team and we are optimistic as to a fast resolution.

Wagmi PR:

• Add conditional in optionalChains - WalletConnectConnector wevm/references#396

Walletconnect discussion:

• Uncaught (in promise) Error: Failed to decrypt WalletConnect#2731

Discord thread:

• Thread between Nicolas Brugneaux and glitch, a WalletConnect maintainer Discord

[nicolasbrugneaux]

Some more insight regarding the wagmi issue: it seems one of the causes for issues is the fact that wagmi implicitely uses the namespaces passed to the provider in order. Here is some pseudocode to illustrate the issue:

We were using chains: [celoAlfajores, celoCannoli, celo]
which roughly translate {requiredChain: celoAlfajores, optionalChains: [celoCannoli, celo] from wagmi's point of view

As you can see this is flawed and celo (our mainnet) should be first in that array.

While this still doesn't fix the Failed to decrypt, it at least fixes another issue that would have been caused by wallets only supporting mainnet and not the testnets.

[nicolasbrugneaux]

Update Tuesday, July 4th (evening CET)

Hello again,

the issue is now mitigated through a temporary fix in the following PR:

• Fix: stcelo v1 WC v2 fix attempts #140

It means the incident is resolved but we had to compromise on performances. It seems either rainbowkit, wagmi, or walletconnect have an issue when minified and optimized through webpack. We disabled these optimizations in order to re-establish WalletConnect capacities. We'll keep investigating to re-enable thee optimizations in order to have a better UX.

Thank you all for your understanding

[nicolasbrugneaux]

Update Thursday, July 6th

Hello again,

the issue is now resolved with minification re-enabled through the following PR:

• fix: reenable minification without swc #141

It was due to a bug in the SWC minifier. Using Babel's minifier instead solves the issue completely.