Skip to content

Vialectrum 3.0.5
Compare
Choose a tag to compare
@romanornr romanornr released this 22 Jan 00:10
· 4675 commits to master since this release
3.0.5
f9b349b
This commit was signed with the committer’s verified signature.
romanornr Romano
GPG key ID: 3F92368F0D21A206
Learn about vigilant mode.
Before you upgrade, make sure you have saved your wallet seed on paper. You can use https://coinomi.com for importing your seed/privkeys

Release 3.0.5 : (Security update)

This is a follow-up to the 3.0.4 release, which did not completely fix
issue #3374. Users should upgrade to 3.0.5.

  • The JSONRPC interface is password protected
  • JSONRPC commands are disabled if the GUI is running, except 'ping',
    which is used to determine if a GUI is already running

Release 3.0.4 : (Security update)

  • Fix a vulnerability caused by Cross-Origin Resource Sharing (CORS)
    in the JSONRPC interface. Previous versions of Electrum are
    vulnerable to port scanning and deanonimization attacks from
    malicious websites. Wallets that are not password-protected are
    vulnerable to theft.
  • Bundle QR scanner with Android app
  • Minor bug fixes

Release 3.0.3

  • Qt GUI: sweeping now uses the Send tab, allowing fees to be set
  • Windows: if using the installer binary, there is now a separate shortcut
    for "Electrum Testnet"
  • Digital Bitbox: added suport for p2sh-segwit
  • OS notifications for incoming transactions
  • better transaction size estimation:
    • fees for segwit txns were somewhat underestimated (#3347)
    • some multisig txns were underestimated
    • handle uncompressed pubkeys
  • fix #3321: testnet for Windows binaries
  • fix #3264: Ledger/dbb signing on some platforms
  • fix #3407: KeepKey sending to p2sh output
  • other minor fixes and usability improvements

Release 3.0.2

  • sweeping minikeys: search for both compressed and uncompressed
    pubkeys
  • fix wizard crash when attempting to reset Google Authenticator
  • fix #3248: fix Ledger+segwit signing
  • fix #3262: fix SSL payment request signing
  • other minor fixes.

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
      Vialectrum 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.

      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 Vialectrum 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.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

4fd682595106d3bdce5eb5add4bd331a  vialectrum-3.0.5.exe
9cc7d275ebd90c6542179062429f821b  vialectrum-3.0.5-portable.exe
8d465794509a2dea1292756501d73eb0  vialectrum-3.0.5-setup.exe
-----BEGIN PGP SIGNATURE-----

iQEyBAEBCAAdFiEE+1u6Oha8avDSoh1hP5I2jw0hogYFAlplLLcACgkQP5I2jw0h
ogYJTQf2PndrfIdVAQY9ZZEDznbR5A4NCuhqlWuYZP94kmuv+Vr5xwqjVNzeMioN
G2WPTQdkweysCcRayKfjQOI+T6R2SSvC9tT0wlFGhBFCxS7C5qonSPR1+xGxAI/u
XHFsMjZ22adBkShKKzNpU966HyAeZ/BxJmIf3QQYGT1fQwuYC7h+bXYEcuDUjjC+
XNOPWlnW+YuULd/2SxwGXwggCDGr6hS0B7IKNRhKFVlknR/ZQ1CoUvzZHKXLLljg
yRvHSAtzEy0vxnuXL2aNEWVnDWMpFkY5jf1nDL8yWnBUUdOwtvsQV7pJfp5XuwdS
ZbyawwbpQ6XZ186sIlTCVTezUnbN
=40xM
-----END PGP SIGNATURE-----
Assets 5
Loading