mirror of
https://github.com/LBRYFoundation/LBRY-Vault.git
synced 2025-09-01 01:35:20 +00:00
update release notes
This commit is contained in:
parent
cb6989cea6
commit
43c808291f
1 changed files with 49 additions and 51 deletions
100
RELEASE-NOTES
100
RELEASE-NOTES
|
@ -1,61 +1,59 @@
|
||||||
# Release 3.2.0 - (unreleased)
|
# Release 3.2.0 - (unreleased)
|
||||||
|
|
||||||
* libsecp256k1: to speed up elliptic curve operations, Electrum can now
|
* If present, libsecp256k1 is used to speed up elliptic curve
|
||||||
utilize the libsecp256k1 library from Bitcoin Core, if present.
|
operations. The library is bundled in the Windows, MacOS, and
|
||||||
Otherwise, as before, python-ecdsa is used. libsecp256k1 is
|
Android binaries. On Linux, it needs to be installed separately.
|
||||||
bundled in the Windows, MacOS, and Android binaries. As we only
|
* Two-factor authentication is available on Android. Note that this
|
||||||
distribute source for Linux, for now, users need to install the library
|
will only provide additional security if one time passwords are
|
||||||
themselves if they desire its benefits.
|
generated on a separate device.
|
||||||
* Two-factor wallets are now implemented for Android.
|
* Semi-automated crash reporting is implemented for Android.
|
||||||
Note that they only provide additional security if the one time
|
* Transactions that are dropped from the mempool are kept in the
|
||||||
passwords are generated on a separate device.
|
wallet as 'local', and can be rebroadcast. Previously these
|
||||||
* Semi-automated crash reporting is now implemented for Android too.
|
transactions were deleted from the wallet.
|
||||||
* Generalized local transactions: an "is mine" input is no longer needed
|
* The scriptSig and witness part of transaction inputs are no longer
|
||||||
to qualify as local, which in practice means that any transaction
|
parsed, unless actually needed. The wallet will no longer display
|
||||||
that drops from the mempool becomes local and is kept. Previously
|
'from' addresses corresponding to transaction inputs, except for
|
||||||
these were deleted from the wallet.
|
its own inputs.
|
||||||
* Wallet logic: the scriptSig and witness part of transactions is no longer
|
* The partial transaction format has been incompatibly changed. This
|
||||||
parsed, unless actually needed, which was in the past occasionally the cause
|
was needed as for partial transactions the scriptSig/witness has to
|
||||||
of getting stuck in infinite "Synchronizing". As the input scripts are not
|
be parsed, but for signed transactions we did not want to do the
|
||||||
parsed, the "from" addresses are not inferred. The wallet history and
|
parsing. Users should make sure that all instances of Electrum
|
||||||
balance logic no longer depend on "from" addresses.
|
they use to co-sign or offline sign, are updated together.
|
||||||
Perhaps most noticeably, as parent transactions are not fetched, and guesses
|
* Signing of partial transactions created with online imported
|
||||||
for the "from" addresses are no longer made, the Qt GUI will not display
|
addresses wallets now supports significantly more
|
||||||
addresses corresponding to the inputs (except for "is mine" inputs).
|
setups. Previously only online p2pkh address + offline WIF was
|
||||||
* The partial transaction format has been incompatibly changed. This was
|
supported. Now the following setups are all supported:
|
||||||
needed as for partial transactions the scriptSig/witness has to be parsed,
|
|
||||||
but for signed transactions we did not want to do the parsing.
|
|
||||||
Users should make sure that all instances of Electrum they use to co-sign
|
|
||||||
or offline sign, are updated together.
|
|
||||||
* Signing of partial transactions created with online imported addresses
|
|
||||||
wallets now supports significantly more setups. Previously only
|
|
||||||
online p2pkh address + offline WIF was supported.
|
|
||||||
Now the following setups are all supported:
|
|
||||||
- online {p2pkh, p2wpkh-p2sh, p2wpkh} address + offline WIF,
|
- online {p2pkh, p2wpkh-p2sh, p2wpkh} address + offline WIF,
|
||||||
- online {p2pkh, p2wpkh-p2sh, p2wpkh} address + offline seed/xprv,
|
- online {p2pkh, p2wpkh-p2sh, p2wpkh} address + offline seed/xprv,
|
||||||
- online {p2sh, p2wsh-p2sh, p2wsh}-multisig address + offline seeds/xprvs
|
- online {p2sh, p2wsh-p2sh, p2wsh}-multisig address + offline seeds/xprvs
|
||||||
(potentially distributed among several different machines)
|
(potentially distributed among several different machines)
|
||||||
Note that for the online address + offline HD secret case, you need the
|
Note that for the online address + offline HD secret case, you need
|
||||||
offline wallet to recognize the address (i.e. within gap limit).
|
the offline wallet to recognize the address (i.e. within gap
|
||||||
Having an xpub on the online machine is still the recommended setup, as this
|
limit). Having an xpub on the online machine is still the
|
||||||
allows the online machine to generate new addresses on demand.
|
recommended setup, as this allows the online machine to generate
|
||||||
* Ledger: offline signing for segwit inputs (#3302)
|
new addresses on demand.
|
||||||
This has already worked for Trezor and Digital Bitbox. Offline segwit
|
* Ledger: offline signing for segwit inputs (#3302) This has already
|
||||||
signing can be combined with online imported addresses wallets.
|
worked for Trezor and Digital Bitbox. Offline segwit signing can be
|
||||||
* Added Revealer plugin. ( https://revealer.cc )
|
combined with online imported addresses wallets.
|
||||||
Revealer is a seed phrase back-up solution. It allows you to create a cold,
|
* Added Revealer plugin. ( https://revealer.cc ) Revealer is a seed
|
||||||
analog, multi-factor backup of your wallet seeds, or of any arbitrary
|
phrase back-up solution. It allows you to create a cold, analog,
|
||||||
secret. The Revealer utilizes a transparent plastic visual one time pad.
|
multi-factor backup of your wallet seeds, or of any arbitrary
|
||||||
* Fractional fee rates: the Qt GUI now displays fee rates with 0.1 sat/byte
|
secret. The Revealer utilizes a transparent plastic visual one time
|
||||||
precision, and also allows this same resolution in the Send tab.
|
pad.
|
||||||
* Hardware wallets: a "show address" button is now displayed in the Receive
|
* Fractional fee rates: the Qt GUI now displays fee rates with 0.1
|
||||||
tab of the Qt GUI. (#4316)
|
sat/byte precision, and also allows this same resolution in the
|
||||||
|
Send tab.
|
||||||
|
* Hardware wallets: a "show address" button is now displayed in the
|
||||||
|
Receive tab of the Qt GUI. (#4316)
|
||||||
* Trezor One: implemented advanced/matrix recovery (#4329)
|
* Trezor One: implemented advanced/matrix recovery (#4329)
|
||||||
* Qt/Kivy: added "sat" as optional base unit
|
* Qt/Kivy: added "sat" as optional base unit.
|
||||||
* Kivy GUI: significant performance improvements when displaying history and
|
* Kivy GUI: significant performance improvements when displaying
|
||||||
address list of large wallets; and transaction dialog of large transactions
|
history and address list of large wallets; and transaction dialog
|
||||||
* Windows: use dnspython to resolve dns instead of socket.getaddrinfo (#4422)
|
of large transactions.
|
||||||
* importing minikeys: use uncompressed pubkey instead of compressed (#4384)
|
* Windows: use dnspython to resolve dns instead of socket.getaddrinfo
|
||||||
|
(#4422)
|
||||||
|
* Importing minikeys: use uncompressed pubkey instead of compressed
|
||||||
|
(#4384)
|
||||||
* SPV proofs: check inner nodes not to be valid transactions (#4436)
|
* SPV proofs: check inner nodes not to be valid transactions (#4436)
|
||||||
* Qt GUI: there is now an optional "dark" theme (#4461)
|
* Qt GUI: there is now an optional "dark" theme (#4461)
|
||||||
* Several other minor bugfixes and usability improvements.
|
* Several other minor bugfixes and usability improvements.
|
||||||
|
|
Loading…
Add table
Reference in a new issue