Using Ledger wallet: unable to start Web3 call after signing Solana message

[srirambv]

Description

Unable to start Web3 call after signing Solana message

Steps to reproduce

1. Initiate a Web3 call
2. Select Solana
3. Select Ledger Solana account to connect
4. Click on Start a Web3 Call
5. Sign the message
6. Shows Error signing message and doesn't start the call

Actual Result

Solana.Ledger.Web3.Call.mp4

Expected Result

Able to start Web3 call without issues

Additional Information

cc: @mrose17 @HEagle18

[bbondy]

Does this reproduce with MetaMask when using Ledger too?

[bbondy]

Sorry I meant Phantom

[srirambv]

Haven't checked with Ledger+Phantom. Will check and update in a comment

[srirambv]

Same issue with Phantom as well but it provides more info as to why its failing rather than just saying Cannont read properties of undefined

[mrose17]

@srirambv - thanks for checking. at least we know we are "ledger compatible with phantom".

all - i don't know what the root cause is here, i'll do a little research. i'll make sure our FAQ notes this limitation.

[mrose17]

@srirambv - can you verify whether "blind signing" is enabled on the Solana Ledger App? if enabled, does the issue occur for either the Brave or Phantom wallets?

[srirambv]

@mrose17 the problem is when trying to join the Solana call on a different browser (Brave/Edge with Phantom) it doesn't recognize the Solana account. It automatically selects Ethereum accounts so no way to get it to perform Solana sign

[mrose17]

i think we are talking about two different things.

the video in the original report above shows someone trying to create a call using a SOL address on a ledger wallet and getting an error. can you reproduce that error with "blind signing enabled?

[mrose17]

@mrose17 the problem is when trying to join the Solana call on a different browser (Brave/Edge with Phantom) it doesn't recognize the Solana account. It automatically selects Ethereum accounts so no way to get it to perform Solana sign

@hadiamjad - can you confirm that when someone goes to join a call that was created with SOL NFT token gating, that the initial error response they get indicates two things: "this is a web3 call" and "use a SOL wallet"? it seems that what is reported here is that the second indication isn't sent or is being ignored...

[srirambv]

the video in the original report above shows someone trying to create a call using a SOL address on a ledger wallet and getting an error. can you reproduce that error with "blind signing enabled?

Yes. even with "blind signing" enabled it still shows the same error message

[mrose17]

to confirm:

• this is for someone creating a room (not joining)
• they are using a ledger wallet in which "blind signing" is enabled on the SOL application on the ledger wallet
• this fails for both the Brave and Phantom wallets

[srirambv]

this is for someone creating a room (not joining)

Yes. Trying to create a room with Solana Ledger fails

they are using a ledger wallet in which "blind signing" is enabled on the SOL application on the ledger wallet

Yes. With blind signing enabled, creating a room it shows the same error as shown in #1090 (comment)

this fails for both the Brave and Phantom wallets

Yes

[mrose17]

@hadiamjad - TL;DR: the ledger hardware wallet doesn't do the kind of signing we want, so this issue is outside of scope for now; however, please look into #1090 (comment) and, if we're not doing this now, please create an issue and then make this change. thanks!

[t98rex]

hello is there an solution to this problem? of-late i'm facing this.
blind signing is enalbled but the signing transaction never makes it to my ledger.

[mrose17]

Hello! I am in the process of reviewing Brave Talk issues and this one is very interesting...

[mrose17]

@srirambv - may i impose you to see if this still reproduces?

[srirambv]

This still seems to be an issue with Ledger accounts

brave_lkXT3hqBCV.mp4