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
This package now supports multiple master key generation algorithms for Trezor hardware wallets, allowing compatibility with different wallet implementations and enabling seamless integration with various existing wallet types.
4
+
5
+
## Supported Master Key Generation Types
6
+
7
+
### 1. ICARUS
8
+
- Standard CIP-3 wallet compatibility mode
9
+
10
+
### 2. ICARUS_TREZOR
11
+
- CIP-3 variant with 24-word mnemonic compatibility
12
+
- This is Trezor's internal default (SDK passes no `derivationType`)
13
+
14
+
### 3. LEDGER
15
+
- Ledger hardware wallet compatibility mode
16
+
- Use this if your wallet was originally created on a Ledger device
17
+
- Enables access to Ledger-generated accounts on Trezor hardware
18
+
19
+
## Key Concept
20
+
21
+
All types use the same derivation path but different master key generation algorithms from the mnemonic. The `derivationType` tells Trezor which algorithm to use.
22
+
23
+
## Usage
24
+
25
+
### Importing Types and Constants
26
+
27
+
All types and constants are fully exportable from their respective packages:
When pairing a Trezor device, follow this discovery pattern to find existing accounts:
98
+
99
+
1.**Try ICARUS first** - Most common for software wallets
100
+
2.**Try ICARUS_TREZOR** - If balance not found and user has 24-word mnemonic
101
+
3.**Try LEDGER** - If user confirms wallet was originally created on Ledger device
102
+
103
+
This is why many wallet UIs show a "Derivation type override" dropdown - to help users discover their existing accounts.
104
+
105
+
## Implementation Details
106
+
107
+
When a non-default derivation type is specified, the SDK sets the appropriate `derivationType` in the `cardanoSignTransaction` call. For the default type, no `derivationType` is sent to Trezor.
108
+
109
+
## Backward Compatibility
110
+
111
+
Existing wallets without a `derivationType` configuration will continue to work as before. No changes are required for existing users.
112
+
113
+
114
+
115
+
## References
116
+
117
+
-**[CIP-1852](https://cips.cardano.org/cip/CIP-1852)**: HD paths and role meanings
118
+
-**[CIP-3](https://cips.cardano.org/cip/CIP-3)**: Master key generation and 24-word compatibility note
119
+
-**[Trezor Forum](https://forum.trezor.io/t/cardano-ada-transaction-signing-error/10466)**: Community discussion on derivation types
0 commit comments