You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a result, you can't connect with that chain.
I believe, exact wallet behaviour varies depending on specific wallet (whether they handle that error or not), but in case of Leap Cosmos wallet, for example, it causes infinite loading.
Steps to Reproduce
It's kinda tricky, because I tried it with custom closed-source WalletConnect+cosmos integration, but these steps must show the issue:
Add your chain info in ./src/chains/cosmos.ts (in CosmosChainData AND CosmosMetadata) and chain Id in./src/constants/default.ts (in DEFAULT_MAIN_CHAINS)
Run it and try to connect reading the QR code with your mobile wallet (again, tested with Leap).
???
?????
???okay it's infinite loading
Expected behaviour
Connects smoothly 🤌
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
The text was updated successfully, but these errors were encountered:
pyncz
changed the title
WalletConnect-incompatible chain ID
WalletConnect incompatible chain ID
Jun 4, 2024
Summary of the Bug
shentu-2.2
chain ID is not compatible with WalletConnect.It can't be added as a chain in WalletConnect's
SignClient
, as it doesn't follow CAIP-2 chain reference standard.As a result, you can't connect with that chain.
I believe, exact wallet behaviour varies depending on specific wallet (whether they handle that error or not), but in case of Leap Cosmos wallet, for example, it causes infinite loading.
Steps to Reproduce
It's kinda tricky, because I tried it with custom closed-source WalletConnect+cosmos integration, but these steps must show the issue:
.env.local
file in/advanced/dapps/react-dapp-v2-cosmos-provider
subdir and setup the env with your project ID:./src/chains/cosmos.ts
(inCosmosChainData
ANDCosmosMetadata
) and chain Id in./src/constants/default.ts
(inDEFAULT_MAIN_CHAINS
)Expected behaviour
Connects smoothly 🤌
For Admin Use
The text was updated successfully, but these errors were encountered: