Request: Update WalletConnect Cloud Registry metadata with mobile deep links

[NBBorislavMalinov]

Summary

Rabby's entry in the WalletConnect Explorer Registry is missing mobile deep links (mobile.native, mobile.universal) and app store links. This causes infinite spinner when users try to connect Rabby on mobile browsers via WalletConnect.

Problem

When a dApp uses WalletConnect and a user selects Rabby on mobile Safari/Chrome:

1. WalletConnect shows "Continue in Rabby" with an infinite spinner
2. The app never opens because there's no deep link registered
3. Users have to manually open the Rabby app and use its built-in browser

Wallet ID in registry: 18388be9ac2d02726dbac9777c96efaac06d744b2f6d580fccdd4127a6d01fd1

Request

Please update Rabby's listing on the WalletConnect Cloud Registry (the old GitHub registry is now archived) with:

1. mobile.native — deep link scheme (e.g., rabby://)
2. mobile.universal — universal link (e.g., https://rabby.io/wc)
3. iOS App Store link — https://apps.apple.com/app/rabby-wallet/id6450663781
4. Android Play Store link — https://play.google.com/store/apps/details?id=com.debank.rabbymobile

The update can be submitted through the WalletConnect Cloud Dashboard.

Impact

This affects all dApps using WalletConnect that want to support Rabby on mobile. We've had to implement a workaround (warning banner) in our app (nebatoken.com) to inform users about this limitation.

References

• WalletConnect Cloud Registry (replaces the archived GitHub registry): https://cloud.walletconnect.com/
• Old archived registry: https://github.com/WalletConnect/walletconnect-registry
• Rabby iOS: https://apps.apple.com/app/rabby-wallet/id6450663781
• Rabby Android: https://play.google.com/store/apps/details?id=com.debank.rabbymobile

Thank you!