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
The ledger integration currently requires that any transaction that submits a staking certificate or withdraws rewards must contain the derivation path for the account it is referencing.
This is problematic as it makes it impossible to manage staking for any address/account that is based on a multisig or Plutus script and where you want to manage the admin-keys with a ledger .
Would it be possible to allow simply signing for an external account with the appropriate warning and details for the user to accept ?
Ps I assume the same set of issues will probably manifest for Governance to
The text was updated successfully, but these errors were encountered:
The ledger integration currently requires that any transaction that submits a staking certificate or withdraws rewards must contain the derivation path for the account it is referencing.
This is problematic as it makes it impossible to manage staking for any address/account that is based on a multisig or Plutus script and where you want to manage the admin-keys with a ledger .
Would it be possible to allow simply signing for an external account with the appropriate warning and details for the user to accept ?
Ps I assume the same set of issues will probably manifest for Governance to
The text was updated successfully, but these errors were encountered: