release notes: minor changes
This commit is contained in:
@@ -27,11 +27,12 @@
|
||||
Electrum.
|
||||
Note that Electrum connections to Nostr relays are only initiated
|
||||
when the user uses the swap service, and the nostr public key used
|
||||
by the client is ephemeral (servers use a persisted identity).
|
||||
by the client is ephemeral. In contrast, swap providers use a
|
||||
persisted identity.
|
||||
|
||||
* Third-party plugins:
|
||||
- Electrum now support the installation of plugins distributed by
|
||||
third parties as ZIP files. While it has long been possible to
|
||||
- Electrum support the installation of plugins distributed by
|
||||
third-parties as ZIP files. While it has long been possible to
|
||||
install third-party plugins when running Electrum from python
|
||||
sources, the same is now possible when using desktop binaries
|
||||
(Windows, MacOS, Linux). Third-party plugins are installed as ZIP
|
||||
@@ -43,12 +44,12 @@
|
||||
administrator permissions on the local machine; a
|
||||
password-derived public key must be written in the system.
|
||||
|
||||
* Lightning anchor channels (#9264): Since sweeping commitment
|
||||
transaction outputs from anchor channels may require external
|
||||
UTXOs, lightning can no longer be enabled in wallets that do not
|
||||
have a software keystore (hardware wallets, watching-only wallets).
|
||||
Existing wallets that are in that situation cannot create new
|
||||
channels. Anchor channels are the default for new channels.
|
||||
* Lightning anchor channels (#9264): Newly created channels use
|
||||
anchor commitments by default. Since sweeping outputs from anchor
|
||||
channels may require external UTXOs, lightning can no longer be
|
||||
enabled in wallets that do not have a software keystore (hardware
|
||||
wallets, watching-only wallets). Existing wallets that are in that
|
||||
situation cannot create new channels.
|
||||
|
||||
* Wallet unlocking (Qt):
|
||||
- Wallets can be unlocked in the Qt GUI. When a password-protected
|
||||
@@ -62,7 +63,7 @@
|
||||
|
||||
* Transaction batching (Qt): When creating a new payment, if the
|
||||
output can be added to an existing mempool transaction, the 'New
|
||||
transaction' window will show a dropdown menu, proposing a list of
|
||||
transaction' window will show a drop-down menu, proposing a list of
|
||||
transactions that can be batched with the current payment. This
|
||||
replaces the previous 'batch' option checkbox, and gives more
|
||||
control to the user.
|
||||
@@ -77,8 +78,8 @@
|
||||
- Non-multisig hardware wallet files can be encrypted with a
|
||||
password, instead of the hardware device.
|
||||
- The option to have a password-protected wallet without file
|
||||
encryption has been removed from the Qt GUI. It is still possible to
|
||||
create such a wallet using the command line
|
||||
encryption has been removed from the Qt GUI. It is still possible
|
||||
to create such a wallet using the command line.
|
||||
|
||||
* Lightning address contacts:
|
||||
- It is now possible to create contacts with (lnurl type) lightning
|
||||
@@ -87,10 +88,10 @@
|
||||
* Accounting rules: In order to properly handle on-chain transactions
|
||||
created by lightning channel force closures, we consider that funds
|
||||
successfully redeemed from a script with several possible
|
||||
recipients have never left the final owner's wallet. This avoids
|
||||
having to write balance changes that are to be cancelled later. The
|
||||
corresponding addresses are rendered in the GUI as 'accounting
|
||||
addresses' (in orange).
|
||||
recipients have never left the final recipient's wallet. This
|
||||
avoids having to write balance changes that are cancelled
|
||||
later. The corresponding addresses are rendered in the GUI as
|
||||
'accounting addresses' (in orange).
|
||||
|
||||
* New plugins:
|
||||
- Nostr Wallet Connect: This plugin allows remote control of
|
||||
@@ -107,26 +108,26 @@
|
||||
documented in the same docstring as the command they belong to.
|
||||
- If the --wallet parameter passed to a command is a simple filename,
|
||||
it is now interpreted as relative to the users wallets directory,
|
||||
rather than to the current working directory
|
||||
rather than to the current working directory.
|
||||
- Plugins may add extra commands to the CLI. Plugin commands must
|
||||
be prefixed with the plugin's internal name
|
||||
- support for hold invoices
|
||||
- support for onion messages
|
||||
be prefixed with the plugin's internal name.
|
||||
- Support for hold invoices.
|
||||
|
||||
* Security:
|
||||
- Mitigate against dust attacks; Add option to avoid spending from used addresses
|
||||
- Restrict process memory access on Linux
|
||||
- Mitigate against dust attacks; Add option to avoid spending from
|
||||
used addresses.
|
||||
- Restrict process memory access on Linux.
|
||||
|
||||
* Networking:
|
||||
- add single server option
|
||||
- The option to connect to a single server has been added to the GUI.
|
||||
|
||||
* Android:
|
||||
- Sweep key feature ported to mobile
|
||||
- Estimate amount when Max is checked
|
||||
- Properly ask for (notification) permission access
|
||||
- Properly ask for (notification) permission access.
|
||||
|
||||
* Hardware wallets:
|
||||
- Coldcard: add feature to upload multisig wallet configuration to Coldcard via USB
|
||||
- Coldcard: add feature to upload multisig wallet configuration to Coldcard via USB.
|
||||
|
||||
|
||||
# Release 4.5.8 (Oct 23, 2024)
|
||||
|
||||
Reference in New Issue
Block a user