BTCPrivate
/
electrum-bitcoinprivate
mirror of https://github.com/BTCPrivate/electrum-bitcoinprivate.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

update release notes

This commit is contained in:
ThomasV 2015-07-21 12:26:51 +02:00
parent a6c65b8997
commit fa867d5792
1 changed files with 13 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
RELEASE-NOTES
View File

@ -1,16 +1,20 @@
# Release 2.4 # Release 2.4
* The Openalias plugin was merged into the main code. * The Openalias/DNSSEC plugin was merged into the main electrum
* The DNSSEC validation procedure (used for OpenAliases) was code. The DNSSEC verification procedure was rewritten. The previous
rewritten. The previous validation method, which was included in validation method, which was part of the OpenAlias plugin, is
the OpenAlias plugin, is vulnerable and should not be trusted vulnerable and should not be trusted (Electrum 2.0 to 2.3).
(Electrum 2.0 to 2.3). * BIP70 payment requests can be signed using Bitcoin keys stored in
* Payment requests can be signed with DNSSEC aliases. This DNS (OpenAlias). The identity of the requestor is verified using
effectively extends BIP70 to user aliases. DNSSEC.
* New 'email' plugin, that enables sending and receiving payment * Payment requests signed with OpenAlias keys can be shared as
requests by email. bitcoin: URIs, if they are simple (a single address-type
output). The BIP21 URI scheme is extended with 'name', 'sig',
'timestamp', 'expiration'.
* Arbitrary m-of-n multisig wallets are supported (n<=15). * Arbitrary m-of-n multisig wallets are supported (n<=15).
* Multisig transactions can be signed with Trezor. * Multisig transactions can be signed with Trezor.
* User-set transaction fees are retained with the '!' shortcut. * User-set transaction fees are retained with the '!' shortcut.
* New 'email' plugin, that enables sending and receiving payment
requests by email.
# Release 2.3.3 # Release 2.3.3
* fix proxy settings (issue #1309) * fix proxy settings (issue #1309)