Specifying required chainIds doesn't seem to work properly #3426
Unanswered
gonzamontiel
asked this question in
Developer Support
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Context
We followed this guidelines to integrate to our Polkadot Dapp. We are trying to filter the wallet connection only to wallets that support polkadot. For this reason we are specifying the following inside the connection params:
Problem
When testing this setup, I tried a connection with LOBSTR wallet (stellar network), expecting to catch some kind of error.
To my surprise, no exception was thrown, but some errors were being logged in console.error.
The problem is that SignClient.connect(), which returns an approval() function, is not failing, and it is returning an actual session with a 'valid' account. I put quotes because the account received has this shape:
"polkadot:91b171bb158e2d3848fa23a9f1c25182:GDDRSQK7ZITHZJZQJMTP4BHSJRZRO6GMMG6HUOOUICO7ZXX764LRQATY"
Which makes no sense to me, since GD...ATY is not a valid polkadot address, but stellar's.
As I said, an error is thrown making evident that this is indeed an invalid connection request and should be rejected. The error is as follows:
I would expect that that the approval() function returned by SignClient.connect() (this one ?) fails or returns an invalid session, but I couldn't find indicators that the session is not valid. What I'm missing?
Session object loos as follows:
Note
This topic is a followup of this discussion.
Beta Was this translation helpful? Give feedback.
All reactions