Topic: News über Electrum wallet - page 3. (Read 2047 times)

# Release 4.3.0 - (August 5, 2022)

 * This version introduces a set of UI modifications that simplify the
   use of Lightning. The idea is to abstract payments from the payment
   layer, and to suggest solutions when a lightning payment is hindered
   by liquidity issues.
    - Invoice unification: on-chain and lightning invoices have been
      merged into a unique type of invoice, and the GUI has a single
      'create request' button. Unified invoices contain both a
      lightning invoice and an onchain fallback address.
    - The receive tab of the GUI can display, for each payment
      request, a lightning invoice, a BIP21 URI, or an onchain
      address. If the request is paid off-chain, the associated
      on-chain address will be recycled in subsequent requests.
    - The receive tab displays whether a payment can be received using
      Lightning, given the current channel liquidity. If a payment
      cannot be received, but may be received after a channel
      rebalance or a submarine swap, the GUI will propose such an
      operation.
    - Similarly, if channels do not have enough liquidity to pay a
      lightning invoice, the GUI will suggest available alternatives:
      rebalance existing channels, open a new channel, perform a
      submarine swap, or pay to the provided onchain fallback address.
    - A single balance is shown in the GUI. A pie chart reflects how
      that balance is distributed (on-chain, lightning, unconfirmed,
      frozen, etc).
    - The semantics of the wallet balance has been modified: only
      incoming transactions are considered in the 'unconfirmed' part
      of the balance. Indeed, if an outgoing transaction does not get
      mined, that is not going to decrease the wallet balance. Thus,
      change outputs of outgoing transactions are not subtracted from
      the confirmed balance. (Before this change, the arithmetic
      values of both incoming and outgoing transactions were added to
      the unconfirmed balance, and could potentially cancel
      each other.)

 * In addition, the following new features are worth noting:
    - support for the Blockstream Jade hardware wallet (#7633)
    - support for LNURL-pay (LUD-06) (#7839)
    - updated trampoline feature bit in invoices (#7801)
    - the claim transactions of reverse swaps are not broadcast until
      the parent transaction is confirmed. This can be overridden by
      manually broadcasting the local transaction.
    - the fee of submarine swap transactions can be bumped (#7724)
    - better error handling for trampoline payments, which should
      improve payment success rate (#7844)
    - channel backups are removed automatically when the corresponding
      channel is redeemed (#7513)

* When creating new requests, reuse addresses of expired requests
   (fixes #7927).
 * Index requests by ID instead of receiving address. This affects the
   following commands: get_request, get_invoice, list_requests,
   list_invoices, delete_request, delete_invoice
 * Trampoline routing: remember routes that have failed. Try other
   routes instead of systematically raising tampoline fees.
 * Fix sweep to_local output from channel backup (#7959)
 * Harden build script for macOS binary: avoid using
   precompiled wheels from PyPI for most packages (#7918)
 * The Windows/AppImage/Android binaries are now built on debian using
   the snapshot.debian.org archive instead of ubuntu. This should help
   with historical reproducibility. (#7926)

# Release 4.3.1 - (August 17, 2022)
 * build: we now also distribute a "source-only"
   Linux-packager-friendly tarball (d0de44a7, #7594), in addition
   to the current "normal" tarball. The "source-only" tarball excludes
   compiled locale files, generated protobuf files, and does not
   vendor our runtime python dependencies (the packages/ folder).
 * fix os.chmod when running in tmpfs on Linux (#7681)
 * (Qt GUI) some improvements for high-DPI monitors (38881129)
 * bring kivy request dialog more in-line with Qt (#7929)
 * rm support of "legacy" (without static_remotekey) LN channels.
   Opening these channels were never supported in a release version,
   only during development prior to the first lightning-capable
   release. Wallets with such channels will have to close them.
   (1f403d1c, 7b8e257e)
 * Qt: fix duplication of some OS notifications on onchain txs (#7943)
 * fix multiple recent regressions:
    - handle NotEnoughFunds when trying to pay LN invoice (#7920)
    - handle NotEnoughFunds when trying to open LN channel (#7921)
    - labels of payment requests were not propagated to
      history/addresses (#7919)
    - better default labels of outgoing txs (#7942)
    - kivy: dust-valued requests could not be created for LN (#7928)
    - when closing LN channels, future (timelocked) txs were not
      shown in history (#7930)
    - kivy: fix deleting "local" tx from history (#7933)
    - kivy: fix paying amountless LN invoice (#7935)
    - Qt: better handle unparseable URIs (#7941)

Mir geht es darum ob man die Standart Wallet oder Multisig nimmt.
Die 2FA ist ja zusätzlich mit Google Auth.

Multi-signature (multisig) refers to requiring multiple keys to authorize a Bitcoin transaction, rather than a single signature from one key.

Für welche von denen sollte man sich entscheiden außer Nr. 4 ?

Also ich nehme in dem Fall die Default Wallet. Die sicherst Du dann ja auch noch mit einem Passwort ab, oder benutzt Du nicht einen Ledger für deine BTC?
Dann müsstest Du sie eh über den Ledger entsperren um den Bestand etc zu sehen.

Für welche von denen sollte man sich entscheiden außer Nr. 4 ?

Der dort vorhandene Link auf http://electrumserv.noip.me/onionservers.txt funktioniert aber nicht. Gibt es eine neue Liste?

Um Electrum mit Tor zu benutzen, benötigst du den Tor-Browser. Installiere diesen von der offiziellen Webseite https://www.torproject.org. Folge den Schritten, die in der Download-Sektion beschrieben sind.

Klicke in Electrum auf den Menüpunkt „Werkzeuge“ -> „Netzwerk“ (oder klicke auf den grünen LED-Knopf in der rechten unteren Ecke) und wähle den Reiter „Proxy“ aus. Wähle „Tor Proxy auf Port 9150 nutzen“. Du kannst nun entweder weiterhin einen regulären öffentlichen Server verwenden, oder im Reiter "Server" eine spezifische Tor .onion-Adresse konfigurieren.

Die zuvor grüne LED sollte nun auf blau wechseln um anzuzeigen, dass du nun über das Tor-Netzwerk verbunden bist.

Using Electrum Through Tor

Please note that when using Electrum through Tor there are two main ways. The first way has the most Privacy but also requires the most trust in the server you are connecting to. This is because normally Electrum connects to a few different servers and downloads block headers and checks that they match. This prevents/makes it more difficult for Rogue servers to send you bad information. However, this can also present a privacy issue because you could be connecting to none .onion servers for these headers.

Thus the two different options are, Connect to 1 server ONLY and get block headers and transaction info from that server. Or Connect to 8 block header servers and connect to 1 .onion server for the general use.

# Release 4.2.0 - (March 16, 2022)
 * The minimum python version was increased to 3.8 (#7661)
 * Lightning:
   - redesigned MPP splitting algorithm (#7202)
   - trampoline: implement multi-trampoline MPP (#7623)
   - implement option_shutdown_anysegwit, and allow dust limits
     below 546 sat (#7542)
   - implement option_channel_type (#7636)
   - implement modern closing negotiation (#7586, #7680)
 * improve support for "lightning:" URIs on all platforms (#7301)
 * Qt GUI:
   - add setting "show amounts with msat precision" (5891e039)
   - add setting "add thousand separators to bitcoin amounts" (#7427)
 * CLI/RPC:
   - implement Unix sockets and make them the default (#7545, #7566)
   - add "bumpfee" command (#7438)
 * Kivy GUI:
   - show network setup on first start before wallet creation (#7464)
   - add "Child Pays For Parent" option (#7487)
   - improved locale handling (22bb52d5, 7cb11ced, 4293d6ec)
 * Hardware wallets:
   - trezor: bump trezorlib to 0.13 (#7590)
   - bitbox02: bump bitbox02 to 6.0, support send-to-taproot (#7693)
   - ledger: support "Ledger Nano S Plus" (#7692)
 * Library:
   - added support for sighash types beside "ALL" (#7453)
   - signmessage: also accept Trezor-type sigs for segwit addrs (#7668)
   - network: make request timeout configurable (#7696)
   - paytomany (onchain txout batching) now allows multiple max("!")
     amounts with specified weights (#7492)
 * Binary builds
   - AppImage: changed base image from ubuntu 16.04 to 18.04 (5d0aa63a)
 * migrated from Travis CI to Cirrus CI (#7431)
 * Lots of other minor bugfixes and usability improvements.

# Release 4.2.1 - (March 26, 2022)
 * Binaries:
   - Windows: we are dropping support for Windows 7. (#7728)
     Version 4.2.0 already unintentionally broke compatibility with
     Win7 and there is no easy way to restore and maintain support.
     Existing users can keep using version 4.1.5 for now, but should
     consider upgrading or changing their OS.
     Win8.1 still works but only Win10 is regularly tested.
   - bump bundled Python version (win, mac, appimage) to 3.9.11,
     (android) to 3.8.13 (1bb7ef92, #7721)
     (note these include a fix to an openssl DOS-vector CVE-2022-0778)
   - windows: bump pyinstaller to 4.10 and wine to 7.0 (#7721)
 * Kivy GUI:
   - fix "Child Pays For Parent" not working on Android (#7723)
   - revert to defaulting the UI language to English (25fee6a6)
 * Qt GUI:
   - macOS: fix opening "Preferences" segfaulting for some (#7725)
   - more resilient startup: better error-handling and fallback (#7447)
 * Library:
   - fix LN error/warning message-handling, and fix regression that
     errors during channel-open were not properly shown in GUI (a92dede4)
   - during LN chan open, do not backup wallet automatically (#7733)
   - Imported wallets: fix delete_address rm-ing too many txs (#7587)
   - fix potential deadlock in wallet.py (d3476b6b)
 * Hardware wallets:
   - ledger: add progress indicator to sign_transaction (#7516)
 * fix the "--portable" flag for AppImage, and for pip installs (#7732)

# Release 4.2.2 - (May 27, 2022)
 * Lightning:
   - watching onchain outputs: significant perf. improvements (#7781)
   - enforce relative order of some msgs during chan reestablishment,
     lack of which can lead to unwanted force-closures (#7830)
   - fix: in case of a force-close containing incoming HTLCs, we were
     redeeming all HTLCs that we know the preimage for. This might
     publish the preimage of an incomplete MPP. (1a5ef554, e74e9d8e)
 * Hardware wallets:
   - smarter pairing during sign_transaction (238619f1)
   - keepkey: fix pairing with device using a workaround (#7779)
 * fix AppImage failing to run on certain systems (#7784)
 * fix "Automated BIP39 recovery" not scanning change paths (#7804)
 * bypass network proxy for localhost electrum server (#3126)

Bisher war für die Verifizierung der Signatur folgendes im Terminal einzugeben:


Nun steht da aber:
Quelle: https://electrum.org/#download

Ist das richtig so? Also nicht die Versionen, sondern das ThomasV und sombernight_releasekey?

---

Our executables are reproducible, and are signed independently by several builders.
We recommend verifying at least two signatures.

wget https://download.electrum.org/4.x.x/Electrum-4.x.x.tar.gz.asc
gpg --verify Electrum-4.x.x.tar.gz.asc Electrum-4.x.x.tar.gz

wget https://download.electrum.org/4.1.5/Electrum-4.1.5.tar.gz.ThomasV.asc
gpg --verify Electrum-4.1.5.tar.gz.ThomasV.asc Electrum-4.1.5.tar.gz
wget https://download.electrum.org/4.1.5/Electrum-4.1.5.tar.gz.sombernight_releasekey.asc
gpg --verify Electrum-4.1.5.tar.gz.sombernight_releasekey.asc Electrum-4.1.5.tar.gz

gpg --keyserver keys.gnupg.net --recv-keys 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6

We found an entry for 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6.

https://keys.openpgp.org/vks/v1/by-fingerprint/6694D8DE7BE8EE5631BED9502BD5824B7F9470E6

gpg --keyserver keys.openpgp.org --recv-keys 6694D8DE7BE8EE5631BED9502BD5824B7F9470E6

gpg: key 2BD5824B7F9470E6: new key but contains no user ID - skipped
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg:        ohne User-ID: 1

Ich wurde heute In-App auf die aktuelle Version hingewiesen... daher hier ein kurzes Update:

Quelle: https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES

Update verlief reibungslos

* Qt GUI:
   - allow restoring from SLIP39 seeds (#6917)

# Release 4.1.5 - (July 19, 2021)
 * Builds/binaries:
   - macOS: the .dmg binary should now be reproducible
 * Kivy/Android: fix paying bip70 invoices (regression) (90579ccf)
 * fix: payment requests not saved if process is killed (6a049d99)
 * Lightning: improve payment success when using trampoline (3a7f5373)
 * add support for signet test network (#7282)
 * Qt GUI:
   - allow restoring from SLIP39 seeds (#6917)
   - rework QR code scanning on Windows and macOS (#7365)
   - support smaller window sizes, decrease minimums (#7385)
 * GUIs: add "funded or unused" filter option to Addresses tab (#5823)

# Release 4.1.4 - (June 17, 2021)
 * Kivy/Android: fix a regression where a non-LN wallet
   could not open the settings (c49d6995)
 * CLI/RPC: fix "close_wallet" command (#7348)

# Release 4.1.3 - (June 16, 2021)
 * Builds/binaries:
   - Android: the binaries (APKs) should now be reproducible (#7263)
   - AppImage: fix some startup issues by including libxcb deps (#7198)
 * Lightning:
   - smarter LN pathfinding (if trampoline is disabled):
     - estimate liquidity in channels using previous attempts (#7152)
     - consider inflight HTLCs and try to route around them (#7292)
   - bugfix: add more safety checks to avoid "batch RBF" feature
     merging LN funding txs (#7298)
   - remove HTLC value upper limit of ~42 mBTC (#7328)
   - Kivy GUI: implement freezing LN channels (11bb39ee)
 * imported wallets: when enabling the "Use change addresses" option,
   change will now be sent to a random unused imported address. (#7330)
   As before, by default, change is sent back to the "from address".
 * seed generation: make sure newly created electrum seeds don't have
   correct bip39 checksum by chance (#6001)
 * other minor fixes

# Release 4.1.2 - (April 8, 2021)
 * Qt GUI:
    - fix some crashes when exiting (#6889)
    - make sure pressing Ctrl-C always quits (c41cd4ae)
 * Kivy GUI (Android):
    - fix bug with scrollbar, again (#7155)
    - 2fa wallets: fix making transactions (#7190)
    - implement freezing addresses (#7178)
 * Android: use more modern application launcher/icon (#7187)

Version 4.0.9: Ist es nicht mehr möglich (bin der Meinung das ging mal) nur die ganzen angezeigten Adressen als csv zu exportieren? Ich finde nur die Möglichkeit alle Adressen mit zugehörigen private keys als csv zu exportieren.

print "\n".join(i for i in wallet.get_receiving_addresses() )

# Release 4.1.1 (April 2, 2021)
 * fix Qt crash with the swap dialog
 * fix Kivy bug with scrollbar (#7155)
 * fix localization issues (#7158 #4621)
 * fix python crash with swaps (#7160)
 * other minor fixes

# Release 4.1.0 - Kangaroo (March 30, 2021)

This version is our second major release with support for the
Lightning Network. While our initial Lightning release was mostly
about implementing the protocol, this release brings features that are
specifically aimed at keeping Electrum lightweight and trustless,
while avoiding single points of failure. Most of the features listed
below are user-visible.
 * The wallet creation wizard no longer asks for a seed type, and
   creates segwit wallets with bech32 addresses. Older seed types can
   still be created with the command line.
 * Paid invoices (both incoming and outgoing) are automatically
   removed from the send/receive lists of the GUI (one confirmation is
   needed for onchain invoices). Once removed from the list, invoice
   details can still be accessed from the transaction history. In Qt,
   invoice lists have been renamed to 'Sending queue' and 'Receiving
   queue'.
 * Lightning:
    - recoverable channels (see below)
    - trampoline payments (see below)
    - support multi-part-payment
    - support upfront-shutdown-script
 * Recoverable channels (option):
   - Recovery data is added to the channel funding transaction using
     an OP_RETURN. This makes it possible to recover a static backup
     of the channel from the wallet seed. Please note that static
     backups only allow users to request a force-close of the channel
     with the remote node, so that funds not locked in HTLCs can be
     recovered. This assumes that the remote node is still online, did
     not lose its data, and accepts to force close the channel.
   - This option is only available for standard wallets with an
     Electrum seed. It is not available for hardware wallets, because
     it requires a deterministic derivation of the nodeID. It is also
     not available in watching-only wallets, for the same reason. If a
     wallet can have recoverable channels but has an old nodeID, users
     who want to use that feature need to close all their existing
     channels, and to restore their wallet from seed.
   - Channel recovery data uses 20 bytes (16 bytes of the remote
     NodeID plus 4 magic bytes) and is encrypted so that only the
     wallet that owns it can decrypt it. However, blockchain analysis
     will be able to tell that the transaction was probably created by
     Electrum.
   - If the 'use recoverable channels' option is enabled, other nodes
     cannot open a channel to Electrum.
   - If a channel is force-closed, the information in the on-chain
     backup is not sufficient to retrieve the funds in the to_local
     output, in case the wallet is lost in a boating accident before
     expiration of the CSV delay. For that reason, an additional
     backup is presented to the user if they force-close a channel.
 * Trampoline routing (option): Trampoline is a solution that allows
   light clients to delegate path-finding on the Lightning Network, so
   that they do not have to download the entire network
   graph. Trampoline routing was originally proposed by Bastien
   Teinturier and is used in the Phoenix wallet. Here is how
   Trampoline works in Electrum:
   - Trampoline is enabled by default, in order to prevent unwanted
     download of the network gossip. If trampoline is disabled, the
     gossip will be downloaded, regardless of the existence of
     channels.
   - Because there is no discovery mechanism for trampoline nodes, the
     list of available trampolines is hardcoded in the client (it will
     remain so until support for trampoline routing is announced in
     gossip). 3 trampoline nodes are currently available on mainnet:
     ACINQ, Electrum and Hodlister.
   - If Trampoline is enabled:
      - payments use trampoline routing.
      - gossip is disabled.
      - the wallet can only open channels with trampoline nodes.
      - pre-existing channels with non-trampoline nodes are frozen for
        sending.
   - There are two types of trampoline payments: legacy and trampoline
     end-to-end. Legacy payments are possible with any receiver, but
     they offer less privacy than end-to-end trampoline
     payments. Electrum decides whether to perform legacy or
     end-to-end based on the features in the invoice:
       - OPTION_TRAMPOLINE_ROUTING_OPT (bit 25) for Electrum
       - OPTION_TRAMPOLINE_ROUTING_OPT_ECLAIR (bit 51) for Eclair/Phoenix
   - When performing a legacy payment, Electrum will add a second
     trampoline node to the route in order to protect the privacy of
     the payer and payee. It will fall back to a single trampoline if
     the two-trampoline strategy has failed for all trampolines.
     (Note: two-trampoline payments are currently not possible if the
     first trampoline is the ACINQ node, and is disabled for that
     node.)
   - Similar to Phoenix, the fee and CLTV delay are found by
     trial-and-error. If there is a second trampoline in the route, we
     use the same fee/CLTV for both. This trial-and-error is
     temporary; the final specification should add fee information in
     the failure messages, so that we will be able to better fine-tune
     trampoline fees.
 * Qt: The increase fee dialog now has advanced options, and offers
   the choice between different RBF strategies.
 * Watchtowers: The 'use_local_watchtower' feature is deprecated, and
   it has been removed from the Qt GUI. The 'use_remote_watchtower'
   setting has been renamed to 'use_watchtower'.
 * Password unification (Android only): When the Android app is
   started, the entered password is checked against all wallets in
   the directory. If the test passes:
    - all wallets are encrypted
    - new wallets will use the unified password
    - password updates are performed on all wallets
   Whether the password is unified can be seen in the GUI: In the
   'Settings' dialog, the description for the password setting is
   'Change password for this wallet' if the password is not unified,
   and becomes 'Change password' if password is unified.
 * Submarine swaps are now available on kivy/android.
 * Android PIN reset: If the password is unified, the PIN can be reset
   by providing the password.
 * Android: on-chain fees have been removed from the settings
   dialog. Instead, the fee slider is shown to the user everytime an
   on-chain transaction will be performed (sending a payment, opening
   a channel, initiating a submarine swap)
 * BIP-0350: use bech32m for witness version 1+ addresses (4315fa43).
   We have supported sending to any witness version since Electrum
   3.0, using BIP-0173 (bech32) addresses. BIP-0350 makes a breaking
   change in address encoding, and recommends using a new encoding
   (bech32m) for sending to witness version 1 and later.
 * Block explorer: allow setting a custom URL in Qt GUI (#6965)

make_seed(128,"","standard")

Edit: Obwohl ich mir gerade die Frage stelle, führt ein "sudo  apt-get update" und "....upgrade" auch eine Aktualisierung d des electrum wallets durch?

Das ist wohl wahr. Das wäre wohl auch ein Minuspunkt für WSL gewesen, da man keine Desktop-Umgebung hat (wobei man die vermutlich auch nachinstallieren könnte und dann via RDP drauf verbinden).

dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart wsl –set-default-version 2
wsl –set-default-version 2

sudo apt update && sudo apt -y upgrade
sudo apt-get purge xrdp
sudo apt install -y xrdp
sudo apt install -y xfce4
sudo apt install -y xfce4-goodies
----------
sudo cp /etc/xrdp/xrdp.ini /etc/xrdp/xrdp.ini.bak
sudo sed -i s/3389/3390/g /etc/xrdp/xrdp.ini
sudo sed -i s/max_bpp=32/#max_bpp=32\nmax_bpp=128/g /etc/xrdp/xrdp.ini
sudo sed -i s/xserverbpp=24/#xserverbpp=24\nxserverbpp=128/g /etc/xrdp/xrdp.ini
echo xfce4-session > ~/.xsession
----------
sudo nano /etc/xrdp/startwm.sh
diese Zeilen mit einem # auskommentieren:
# test -x /etc/X11/Xsession && exec /etc/X11/Xsession
# exec /bin/sh /etc/X11/Xsession

diese Zeilen hinzufügen:
# xfce
startxfce4