You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, CIP-105/CIP-1852 suggest to use the derivation path structure: m / purpose' / coin_type' / account' / role / index
with the following logic for roles:
when exporting hw signing files from a ledger on fw v1.1.2 and cardano-app v7.1.2 using e.g. the above logic to get DRep keys, it fails, because of _"Details: DeviceStatusError: Action rejected by Ledger's security policy"_
Ledger's security policy seems to reject roles different from 0, 1, 2 . I'm not sure if "Ledger's security policy" is global within the Ledger fw, or if this is solvable through the Ledger Cardano App. If the latter is the case, then this issue belongs to elsewhere, but if its the former, it could get very tricky.. Dont think Ledger would loosen this policy for Cardano Governance alone..
Havent tested with Trezor, or with other HW wallets.
The text was updated successfully, but these errors were encountered:
this works fine in my scripts: ${cardanohwcli} address key-gen --path 1852H/1815H/${accNo}H/3/${idxNo} --verification-key-file ${drepName}.drep.vkey --hw-signing-file ${drepName}.drep.hwsfile
Hi,
CIP-105/CIP-1852 suggest to use the derivation path structure:
m / purpose' / coin_type' / account' / role / index
with the following logic for roles:
0
1
2
3
4
5
when exporting hw signing files from a ledger on fw v1.1.2 and cardano-app v7.1.2 using e.g. the above logic to get DRep keys, it fails, because of
_"Details: DeviceStatusError: Action rejected by Ledger's security policy"_
Ledger's security policy seems to reject roles different from
0, 1, 2
. I'm not sure if "Ledger's security policy" is global within the Ledger fw, or if this is solvable through the Ledger Cardano App. If the latter is the case, then this issue belongs to elsewhere, but if its the former, it could get very tricky.. Dont think Ledger would loosen this policy for Cardano Governance alone..Havent tested with Trezor, or with other HW wallets.
The text was updated successfully, but these errors were encountered: