Recommended Update
Stable release update 2 with the following changes:
- Added support for derivation path from Kaspa as wallet
v1
and Karlsen as walletv2
(see backward compatibility below) - Added new command line option
-l
(short) or--legacy
(long) to thecreate
subcommand (see backward compatibility below) - Switched cointype in bip39 derivation to
121337
(see backward compatibility below) - Changed
karlsenwallet
listen port from 8082 to 9182 - Fixed
karlsend
andkarlsenminer
Go traces - Fixed all stability and integration tests
- Fixed crash in
karlsenminer
- Fixed race in gRPC client
send
,recv
andclose
handler - Updated Go modules and dependencies
- Issues closed: #6, #7, #13, #17, #19, #25, #26, #34, #36, #37, #38, #40
Breaking Changes
With the complete decoupling of Karlsen from Kaspa, we've introduced several changes which may require attention from node operators. If you are using --loglevel
to specify different subsystem verbosity levels, you need to switch KASD=
to KLSD=
otherwise node startup will fail with: The specified subsystem [KASD] is invalid
.
Backward Compatibility
Following the recent transition from Kaspa coin type 111111
to Karlsen coin type 121337
- a change already documented on https://github.com/satoshilabs/slips/blob/master/slip-0044.md - we're in the process of adopting our specific derivation path. This step is crucial for most integrations that do not operate a node daemon, such as hardware wallets, to ensure address compatibility across different platforms. A unique derivation path is essential for this purpose.
We currently have wallets that use the old coin type, necessitating support for both the legacy and new derivation paths. To facilitate this, a new command line option has been introduced for the create
subcommand: -l
(short) or --legacy
(long). Here's how it functions:
- By default, the command creates or imports a version 2 wallet using the new coin type
121337
. - When the legacy option is invoked, it creates or imports a version 1 wallet with the original coin type
111111
.
Although wallets with version 1 will remain operational, migrating KLS to a newly established version 2 wallet is strongly advised for future compatibility with both software and hardware wallets.
Thanks
Thanks to everyone who directly contributed to this release: