Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id B0639A59 for ; Thu, 2 Nov 2017 09:56:18 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8FF0D1A0 for ; Thu, 2 Nov 2017 09:56:17 +0000 (UTC) X-Originating-IP: 178.19.221.38 Received: from [10.10.42.112] (unknown [178.19.221.38]) (Authenticated sender: thomasv@electrum.org) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 0E73A1720A5 for ; Thu, 2 Nov 2017 10:56:15 +0100 (CET) To: "bitcoin-dev@lists.linuxfoundation.org" From: Thomas Voegtlin Message-ID: Date: Thu, 2 Nov 2017 10:56:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: [bitcoin-dev] Electrum 3.0 release X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Nov 2017 09:56:18 -0000 Electrum 3.0 was tagged and released yesterday night. Release notes: # Release 3.0 - Uncanny Valley (November 1st, 2017) * The project was migrated to Python3 and Qt5. Python2 is no longer supported. If you cloned the source repository, you will need to run "python3 setup.py install" in order to install the new dependencies. * Segwit support: - Native segwit scripts are supported using a new type of seed. The version number for segwit seeds is 0x100. The install wizard will not create segwit seeds by default; users must opt-in with the segwit option. - Native segwit scripts are represented using bech32 addresses, following BIP173. Please note that BIP173 is still in draft status, and that other wallets/websites may not support it. Thus, you should keep a non-segwit wallet in order to be able to receive bitcoins during the transition period. If BIP173 ends up being rejected or substantially modified, your wallet may have to be restored from seed. This will not affect funds sent to bech32 addresses, and it will not affect the capacity of Electrum to spend these funds. - Segwit scripts embedded in p2sh are supported with hardware wallets or bip39 seeds. To create a segwit-in-p2sh wallet, trezor/ledger users will need to enter a BIP49 derivation path. - The BIP32 master keys of segwit wallets are serialized using new version numbers. The new version numbers encode the script type, and they result in the following prefixes: * xpub/xprv : p2pkh or p2sh * ypub/yprv : p2wpkh-in-p2sh * Ypub/Yprv : p2wsh-in-p2sh * zpub/zprv : p2wpkh * Zpub/Zprv : p2wsh These values are identical for mainnet and testnet; tpub/tprv prefixes are no longer used in testnet wallets. - The Wallet Import Format (WIF) is similarly extended for segwit scripts. After a base58-encoded key is decoded to binary, its first byte encodes the script type: * 128 + 0: p2pkh * 128 + 1: p2wpkh * 128 + 2: p2wpkh-in-p2sh * 128 + 5: p2sh * 128 + 6: p2wsh * 128 + 7: p2wsh-in-p2sh The distinction between p2sh and p2pkh in private key means that it is not possible to import a p2sh private key and associate it to a p2pkh address. * A new version of the Electrum protocol is required by the client (version 1.1). Servers using older versions of the protocol will not be displayed in the GUI. * By default, transactions are time-locked to the height of the current block. Other values of locktime may be passed using the command line. -- Electrum Technologies GmbH / Waldemarstr 37a / 10999 Berlin / Germany Sitz, Registergericht: Berlin, Amtsgericht Charlottenburg, HRB 164636 Geschäftsführer: Thomas Voegtlin