@romanornr romanornr released this Sep 4, 2018 · 279 commits to master since this release

Assets 5

Release 3.2.2 - Satoshi's Vision (September 4, 2018)

  • Fix DNS resolution on Windows

  • Fix websocket bug in daemon

  • fix Windows binaries: due to build process changes, the locale files
    were not included; the language could not be changed from English

  • fix Linux distributables: wordlists were not included (#4475)

  • If present, libsecp256k1 is used to speed up elliptic curve
    operations. The library is bundled in the Windows, MacOS, and
    Android binaries. On Linux, it needs to be installed separately.

  • Two-factor authentication is available on Android. Note that this
    will only provide additional security if one time passwords are
    generated on a separate device.

  • Semi-automated crash reporting is implemented for Android.

  • Transactions that are dropped from the mempool are kept in the
    wallet as 'local', and can be rebroadcast. Previously these
    transactions were deleted from the wallet.

  • The scriptSig and witness part of transaction inputs are no longer
    parsed, unless actually needed. The wallet will no longer display
    'from' addresses corresponding to transaction inputs, except for
    its own inputs.

  • The partial transaction format has been incompatibly changed. This
    was 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 seed/xprv,
    • online {p2sh, p2wsh-p2sh, p2wsh}-multisig address + offline seeds/xprvs
      (potentially distributed among several different machines)
      Note that for the online address + offline HD secret case, you need
      the offline wallet to recognize the address (i.e. within gap
      limit). Having an xpub on the online machine is still the
      recommended setup, as this allows the online machine to generate
      new addresses on demand.
  • Segwit multisig for bip39 and hardware wallets is now enabled.
    (both p2wsh-p2sh and native p2wsh)

  • Ledger: offline signing for segwit inputs (#3302) This has already
    worked for Trezor and Digital Bitbox. Offline segwit signing can be
    combined with online imported addresses wallets.

  • Added Revealer plugin. ( https://revealer.cc ) Revealer is a seed
    phrase back-up solution. It allows you to create a cold, analog,
    multi-factor backup of your wallet seeds, or of any arbitrary
    secret. The Revealer utilizes a transparent plastic visual one time
    pad.

  • Fractional fee rates: the Qt GUI now displays fee rates with 0.1
    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)

  • Qt/Kivy: added "sat" as optional base unit.

  • Kivy GUI: significant performance improvements when displaying
    history and address list of large wallets; and transaction dialog
    of large transactions.

  • 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)

  • Qt GUI: there is now an optional "dark" theme (#4461)

  • Several other minor bugfixes and usability improvements.

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

5fccc803b16df9aef5c9b0705e373e8d0af9c72349e0d68ddbe19fb5c90f3335  vialectrum-3.2.2-1.exe
1d1e4d1b330dd9f0e7d7f0204feb0918f2ed8b0f01565382a8d7beeb50d94f72  vialectrum-3.2.2-1-portable.exe
3a145f564e11b6090842a533854ffd60492e2bea7f288d9b768fa23cb724170d  vialectrum-3.2.2-1-setup.exe
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE+1u6Oha8avDSoh1hP5I2jw0hogYFAluOaqYACgkQP5I2jw0h
ogbgWQgAtFaOMDpNO3Z9PAtw4bzbYzs6Oklr8uFqtplrDEK/c4Gm0xtKmErEDNNd
Es6fOEmvhwUDzIdWh3ewW682w5fCFwEyaPLRj9ZcxhUc1qXk6kL9j0e1PdQ+mTIX
+IxgObzNWNmWc5Q8H4P0mm0622O5CdjkvSEheNvY3aqEO1QGtBdA2byhdiYpQype
cjE6bQbbOlN/Rlqll4pT+icsdYY9oALtU2iV/IQP+zCy+IHsEufqxMVWE8Ct0Qc6
eYMaKJ1ar+xDHYvDtpnBByoJf5Tq/7RMSu+aRNACc9cI7i5gOOa+Gn5L7Mbs+Qix
tkJ0ttsS4iUAgsx8S17IzvDWQHdz1w==
=LCKY
-----END PGP SIGNATURE-----

@romanornr romanornr released this Apr 27, 2018 · 709 commits to master since this release

Assets 5

Release 3.1.3.1 - (April 27, 2018)

  • support https://revealer.cc

  • Qt GUI: seed word auto-complete during restore

  • Android: fix some crashes

  • performance improvements (wallet, and Qt GUI)

  • hardware wallets: show debug message during device scan

  • Digital Bitbox: enabled BIP84 (p2wpkh) wallet creation

  • add regtest support (via --regtest flag)

  • other minor bugfixes and usability improvements

  • Kivy/android: request PIN on startup

  • Improve OSX build process

  • Fix various bugs with hardware wallets

  • Other minor bugfixes

  • fix #4031: Trezor T support

  • partial fix #4060: proxy and hardware wallet can't be used together

  • fix #4039: can't set address labels

  • fix crash related to coinbase transactions

  • MacOS: use internal graphics card

  • fix openalias related crashes

  • speed-up capital gains calculations

  • hw wallet encryption: re-prompt for passphrase if incorrect

  • other minor fixes.

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

a36dc06ed49b476c1f2f4489d04fcbcd  dist/vialectrum-3.1.3.1.exe
6bd5ca191b61b705c223e9f240a24990  dist/vialectrum-3.1.3.1-portable.exe
f08bfe55b91bc3c3937ce3c4a7fdcee9  dist/vialectrum-3.1.3.1-setup.exe
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE+1u6Oha8avDSoh1hP5I2jw0hogYFAlrjQOEACgkQP5I2jw0h
ogZSEAf/UAs/j+b2xJJDYdd7JuHD1iwLCJFQ9u4/rP+lMu9RZ1Kvw+9GD5NInnG8
kUXBxNCoPKwXdvL2hzfOoFrr+qqsT91KLNWcCPh4lZBf69EGTG+wBF5DDYDgi1oX
SGsmmZqg4esb/8cnTHTWlxu0EVpvKiPb0+ZWDXWEdqvOUR7rl0zVwHRdtBbZMVvt
4oT1svi9TO5qM5MDaGhK1+f07awvMpKiL/V4uuy9WZRoCbZvoYUVt3zhYFdVX0bc
EJLCUxNaboRqDFwkmeY6V0n+fJ7sJeIWGfFS1/1Mme7Fw0iS0m4RNrTuRjLW3wyO
OUnq4fyYxaNwmZPhnKlxePrU8AqBmQ==
=HZo1
-----END PGP SIGNATURE-----

@romanornr romanornr released this Mar 14, 2018 · 934 commits to master since this release

Assets 5

Release 3.1 - (March 14, 2018)

  • Memory-pool based fee estimation. Dynamic fees can target a desired
    depth in the memory pool. This feature is optional, and ETA-based
    estimates from Viacoin Core are still available. Note that miners
    could exploit this feature, if they conspired and filled the memory
    pool with expensive transactions that never get mined. However,
    since the Electrum client already trusts an Electrum server with
    fee estimates, activating this feature does not introduce any new
    vulnerability. In addition, the client uses a hard threshold to
    protect itself from servers sending excessive fee estimates. In
    practice, ETA-based estimates have resulted in sticky fees, and
    caused many users to overpay for transactions. Advanced users tend
    to visit (and trust) websites that display memory-pool data in
    order to set their fees.
  • Capital gains: For each outgoing transaction, the difference
    between the acquisition and liquidation prices of outgoing coins is
    displayed in the wallet history. By default, historical exchange
    rates are used to compute acquisition and liquidation prices. These
    values can also be entered manually, in order to match the actual
    price realized by the user. The order of liquidation of coins is
    the natural order defined by the blockchain; this results in
    capital gain values that are invariant to changes in the set of
    addresses that are in the wallet. Any other ordering strategy (such
    as FIFO, LIFO) would result in capital gain values that depend on
    the presence of other addresses in the wallet.
  • Local transactions: Transactions can be saved in the wallet without
    being broadcast. The inputs of local transactions are considered as
    spent, and their change outputs can be re-used in subsequent
    transactions. This can be combined with cold storage, in order to
    create several transactions before broadcasting them. Outgoing
    transactions that have been removed from the memory pool are also
    saved in the wallet, and can be broadcast again.
  • Checkpoints: The initial download of a headers file was replaced
    with hardcoded checkpoints. The wallet uses one checkpoint per
    retargeting period. The headers for a retargeting period are
    downloaded only if transactions need to be verified in this period.
  • The 'privacy' and 'priority' coin selection policies have been
    merged into one. Previously, the 'privacy' policy has been unusable
    because it was was not prioritizing confirmed coins. The new policy
    is similar to 'privacy', except that it de-prioritizes addresses
    that have unconfirmed coins.
  • The 'Send' tab of the Qt GUI displays how transaction fees are
    computed from transaction size.
  • The wallet history can be filtered by time interval.
  • Replace-by-fee is enabled by default. Note that this might cause
    some issues with wallets that do not display RBF transactions until
    they are confirmed.
  • Watching-only wallets and hardware wallets can be encrypted.
  • Semi-automated crash reporting
  • The SSL checkbox option was removed from the GUI.
  • The Trezor T hardware wallet is now supported.
  • BIP84: native segwit p2wpkh scripts for bip39 seeds and hardware
    wallets can now be created when specifying a BIP84 derivation
    path. This is usable with Trezor and Ledger.
  • Windows: the binaries now include ZBar, and QR code scanning should work.
  • The Wallet Import Format (WIF) for private keys that was extended in 3.0
    is changed. Keys in the previous format can be imported, compatibility
    is maintained. Newly exported keys will be serialized as
    "script_type:original_wif_format_key".
  • BIP32 master keys for testnet once again have different version bytes than
    on mainnet. For the mainnet prefixes {x,y,Y,z,Z}|{pub,prv}, the
    corresponding testnet prefixes are {t,u,U,v,V}|{pub,prv}.
    More details and exact version bytes are specified at:
    https://github.com/spesmilo/electrum-docs/blob/master/xpub_version_bytes.rst
    Note that due to this change, testnet wallet files created with previous
    versions of Electrum must be considered broken, and they need to be
    recreated from seed words.
  • A new version of the Electrum protocol is required by the client
    (version 1.2). Servers using older versions of the protocol will
    not be displayed in the GUI.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

63778eba43ba7eac1d2aa71079ec1cd539d6c8764287a559126280a18f71fafd  vialectrum-3.1.exe
0db4c62f4126f9617be5e556c9edaa6943921ea4a2f5d4c85a126da1b8728847  vialectrum-3.1-portable.exe
b8aef1cbf25e8d8a389848a5366e86e9bfdffb4ec15092d28a21462302a1e213  vialectrum-3.1-setup.exe
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE+1u6Oha8avDSoh1hP5I2jw0hogYFAlqpmMsACgkQP5I2jw0h
ogbR5wf/YCjsggkk0ri/PvvANtpVYAraHPf2epN06pVtmC9fmYrCpFT7zggdcmBL
JcuQHaGjoodVJXPBQehxOXs1vwiyQK2DEnnffcCYmGEVRJp+C0UCohazLLUW8mSH
RIn96nnoli8YL2XTyGRUhWuBjCgdBX85EeqOWvS+Ut66A09FJNZ1ynt9QCspoUx/
KDizTOMzM1ZLlmSsurT8McXys3Dh2PladN1OSF4/7Gm24+GRGl1Q1inYiRGd4HN9
irhxuFpaR0x3IajZBKrDE+xoyMVS0wLae6AoZ6ikVICvBREvkmLycbUq2QhZzXyV
Qi+l/O6ge1pEOe/KjAegiRnOTzX/5Q==
=pvMt
-----END PGP SIGNATURE-----

@romanornr romanornr released this Jan 22, 2018 · 1443 commits to master since this release

Assets 5
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-----

@romanornr romanornr released this Apr 11, 2017 · 2789 commits to master since this release

Assets 5
Before you upgrade, make sure you have saved your wallet seed on paper.
  • Use instantly: Electrum doesn't download the blockchain or require your computer to sync with the network. Instead, it is maintained on a tamper-proof, remote server.
  • Safe: Your unique twelve word pass-phrase and private keys are never sent to the vialectrum servers. All information received from the server is verified using Simplified Payment Verification (SPV).
  • Forgiving: Never be concerned about losing your wallet! With your unique twelve-word seed, you can always recover and restore your wallet...even if you sustain the worst of hardware or software failures.
    Cold storage: Use vialectrum to generate and manage your secure offline wallets, enabling you to take some or all of your funds completely offline.
  • Accessible: Export your private keys to other Viacoin clients, at your convenience.
  • Segwit: Experience an observable change in the average size of blocks, as a significant amount of transactional data is removed from the traditional block structure.
  • Add-ons: Vialectrum supports third-party plugins: Multisig services, Hardware wallets (Trezor & Ledger), etc.
  • Multisig: Split the permission to spend your coins between several wallets.
  • No Lock-In: You can export your private keys and use them in the Viacoin Core wallet.
  • Two factor authentication: Be safe from malware Use two-factor authentication.