Content
@
0 reply
1 recast
1 reaction
Nick T
@nt
I love Rainbow and use it exclusively, but I get crippled every 10th time I try to connect wallet or execute a transaction from a connected web dApp. Transactions just don't show up, or show up after restarting the app, and cycling connection state. Doesn't seem like an exclusive Rainbow problem but something that haunts all mobile wallets. @mikedemarais.eth is there a technical reason behind this?
1 reply
0 recast
9 reactions
mike rainbow (rainbow mike) ↑
@mikedemarais.eth
technical reason is walletconnect :/ i feel your pain, i hate that experience more than anybody. the pain of unreliable connections to dapps is why we built Rainbow’s in-app web browser, which lets you interact with dapps without needing to bounce back and forth w walletconnect
4 replies
1 recast
11 reactions
mike rainbow (rainbow mike) ↑
@mikedemarais.eth
https://warpcast.com/rainbow/0x08e2bb5a
1 reply
0 recast
1 reaction
Nick T
@nt
Is it possible to circumvent this via proprietary flows within Rainbowkit? I'm assuming you guys don't do this as I have similar issues when connecting through the "Rainbow" option. Seems like a Walletconnect competitor that focuses on reliability is a huge opportunity 👀
2 replies
0 recast
1 reaction
Glitch
@glitch
WalletConnect is an open source protocol and we always welcome contributors to it. Btw WalletConnect Link Mode release is close, this will improve a lot the communication performance on mobile 👍🏻
0 reply
0 recast
2 reactions
Q🎩
@qsteak.eth
Feels like that one store making you take you license out of the clear part to verify.
0 reply
0 recast
0 reaction
