POA Forum

Hardware wallets are not working with RSK

Hi,

After some user reports, I tested the functionality and:

  • Ledger doesn’t work (TransportStatusError: Ledger device: UNKNOWN_ERROR (0x6804))
  • Trezor works but derives addresses with ETH dpath (RSK dpath is different)

Please let me know if you need help to tackle this issues.

Best

Thanks for reporting. We will take a look into it.

Thanks @igorbarinov, let me know if you need me to test the fix (we have Trezor and Ledger devices here)

Hi @Alejandro_Cavallero. Here is the fix for paths derivation for HD wallets accounts in case of RSK and ETC chains https://github.com/poanetwork/nifty-wallet/pull/317. Here is the zipped bundle with extension with this fix https://github.com/poanetwork/nifty-wallet/blob/6c3d143a4ff2e2b56c497fe20ed0eec80e84c741/NW_4.11.10_chrome_HD_path_fix.zip. I will appreciate If you could let me know if it works fine for you with HD wallets with this update. What I noticed, that I am unable to switch to Ledger Legacy from Ledger Live. Apparently, Ledger Legacy has a different path derivation? Do you know, maybe?

In order to test local Chrome extensions, you need to go to chrome://extensions page. Click “Load unpacked” button and choose the folder with extension from the archive, which I attached (assuming you unzipped it previously).

@viktorbaranov thanks, I will check it.
I guess this issue is related to this one: "Reveal seed words" derives with ETH dpath instead of RSK

@viktorbaranov I checked with Trezor T and it still derives ETH addresses when connected to RSK Mainnet (and the same happens with ETC)

I checked with the tracing that correct path comes to HD wallet creation method with that PR. How do you check that ETH addresses actually derived? Did behaviour change for Ledger?

@viktorbaranov I couldn’t test with Ledger yet.
When I’m connected to RSK mainnet and I choose Trezor, it opens a page requesting permission to export the public key with this message: “Export public key of Ethereum account #1”. If it worked ok, it would say “Export public key of RSK account #1”.

And I checked the derived addresses doing the same with MEW, for example

I checked with Ledger and same error msg: Ledger device: UNKNOWN_ERROR (0x6804)

@Alejandro_Cavallero are you sure that you are in a local extension and not in the extension from the Chrome web store?

Yes @viktorbaranov, it’s the zip you sent

@Alejandro_Cavallero, yes, I reproduced the issue. I fixed in this commit https://github.com/poanetwork/nifty-wallet/pull/317/commits/3a964cbe23b35e74b2c197165ad82ae8b3d724d4 and updated zip archive: https://github.com/poanetwork/nifty-wallet/blob/3a964cbe23b35e74b2c197165ad82ae8b3d724d4/NW_4.11.10_chrome_HD_path_fix.zip. Please let me know how does it work with Ledger/Trezor now.

When I’m connected to RSK mainnet and I choose Trezor, it opens a page requesting permission to export the public key with this message: “Export public key of Ethereum account #1”. If it worked ok, it would say “Export public key of RSK account #1”.

Unfortunately, we have no control on this page because it is hosted on Trezor’s end.

1 Like

@viktorbaranov same issues

1 Like

Any news about this?

@Alejandro_Cavallero working on it. Indeed, the issue still exists. For unknown yet reason, accounts are derived from ETH path. I need to run more tests to not bother you with wrong bundles. I plan to deliver the final update this week. It should cover the issues with hardware wallets path.

@Alejandro_Cavallero Here is the bundle https://github.com/poanetwork/nifty-wallet/blob/1416ffa07ec177378fa64234203e5e33088a072a/NW_4.11.10_chrome_HD_path_fix.zip with, I hope, the final fix for HD wallets’ support for RSK chains. It tested with Ledger and Trezor. The behaviour is the same, that you experience with MyCrypto switching to RSK providers. Please, let me know your experience with this bundle. If it works fine now with HD wallets, I will start work on the next issue with accounts derivation from a mnemonic phrase.

1 Like

Now it’s working! Good job!

2 Likes