Open glitch-txs opened 1 year ago
Not sure if this will help, but part of what you specify for connection params
chains: [polkadot: 'polkadot:91b171bb158e2d3848fa23a9f1c25182'],
should look like this
chains: ['polkadot:91b171bb158e2d3848fa23a9f1c25182'],
Not sure if this will help, but part of what you specify for connection params chains: [polkadot: 'polkadot:91b171bb158e2d3848fa23a9f1c25182'], should look like this chains: ['polkadot:91b171bb158e2d3848fa23a9f1c25182'],
Oops sorry, my bad, I manually changed the parameters in the example for illustrating the post, bc we are building the object programmatically. But we are passing the right value, thanks.
Hi, any news on this ? Could you guys take a look @glitch-txs ?
Hi could you share a MRE?
Hi, sorry my late response. While not exactly an MRE, our current code is not that hard to follow. The configuration that we use is here. We instantiate the client here and we grab the addresses from the response here.
This code can be tested here, if you click in "Connect Wallet", and then the Wallet Connect option. You'll need a way to connect to a non-polkadot wallet (I used LOBSTR to try it out). I specifically added a log with the session information returned.
Thanks in advance!
Discussed in https://github.com/orgs/WalletConnect/discussions/3426