FR - Add a flag to change the default derivation method for Trezor devices

[gitmachtl]

As stated in trezor/trezor-firmware#1783 there are a number of different seed derivation schemes used in Cardano. But the 24 word seed implementation had a bug in Trezor. There was a fix for that, and the latest version is using Icarus. However the version with the Bug "Icarus_Legacy" is the default fallback method used in cardano-hw-cli. So if a Trezor device is used with 24 seed words, the derived keys/addresses via cardano-hw-cli don't line up anymore with the ones shown in Trezor-Suite right now. And using addresses generated via hw-cli results in "Cardano Legacy" addresses within Trezor-Suite.

Feature request is to add a flag that would tell cardano-hw-cli to use the newer "Icarus" method and not the "Icarus_Legacy" method.

@refi93

[janmazak]

@gitmachtl
Well, cardano-hw-cli is a pass-through tool with respect to derivation paths and derived keys, it has no control whatsoever about how keys are derived in the connected HW device (ledger/trezor), and it never derives any keys on its own.

[davidmisiak]

@janmazak I think we can control the derivation scheme by setting the derivationType parameter on Trezor Connect calls (docs e.g. here).

[gitmachtl]

Hmm... i am using trezor-bridge on the cli, is this also available in bridge?

[gitmachtl]

@gitmachtl Well, cardano-hw-cli is a pass-through tool with respect to derivation paths and derived keys, it has no control whatsoever about how keys are derived in the connected HW device (ledger/trezor), and it never derives any keys on its own.

I am just wondering how Trezor-Suite can also show the "Ledger" part without knowing the root-key? is Trezor-Suite requesting this from the device in a silenced mode? Or is there also a "Ledger" style flag for the derivationType implemented?

[davidmisiak]

Hmm... i am using trezor-bridge on the cli, is this also available in bridge?

Yes, bridge only forwards commands generated by Trezor Connect.

[davidmisiak]

Feature added in #135