# Release 4.3.3 - (January 3, 2023)
 * Lightning:
   - fix handling failed HTLCs in gossip-based routing (#7995)
   - fix LN cooperative-chan-close to witness v1 addr (#8012)
 * PSBTs:
   - never put ypub/zpub in psbts, only plain xpubs (#8036)
   - for witness v0 txins, put both UTXO and WIT_UTXO in psbt (#8039)
 * Hardware wallets:
   - Trezor: optimize signing speed by not serializing tx (#8058)
   - Ledger:
     - modify plugin to support new bitcoin app v2.1.0 (#8041),
     - added a deprecation warning when using Ledger HW.1 devices.
       Ledger itself stopped supporting HW.1 some years ago, and it is
       becoming a maintenance burden for us to keep supporting it.
       Please migrate away from these devices. Support will be removed
       in a future release.
 * Binaries:
   - tighten build system to only use source pkgs in more places
     (#7999, #8000)
   - Windows:
     - use debian makensis instead of upstream windows exe (#8057)
     - stop using debian sid, build missing dep instead (98d29cba)
   - AppImage: fix failing to run on certain systems (#8011)
 * commands:
   - getinfo() to show if running in testnet mode (#8044)
   - add a "convert_currency" command (for fiat FX rate) (#8091)
 * Qt wizard: fix QR code not shown during 2fa wallet creation (#8071)
 * rework Tor-socks-proxy detection to reduce Tor-log-spam (#7317)
 * Android: add setting to enable debug logs (#7409)
 * fix payserver (merchant) js for electrum 4.3 invoice api (0fc90e07)
 * bip21: more robust handling of URIs that include a "lightning" key
   (ac1d53f0, 2fd762c3, #8047)


# Release 4.3.2 - (September 26, 2022)
 * 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)

Na mal schauen was sich die nächsten Wochen ergeben. Ich habe dort allerdings auch nichts mehr liegen.

Polizisten stürmen die Büros des Kryptoverleihers. Der Vorwurf: Terrorismusfinanzierung. Das Unternehmen sieht eine “koordinierte Attacke”.

Laut einem eigenen Audit bestehen fast 2,8 Milliarden US-Dollar an Zahlungsverpflichtungen. Laut Datenanalyst Cryptus Christ halte Nexo aber nur Assets im Wert von rund 365 Milliarden US-Dollar. Besonders brisant: Rund 315 Millionen US-Dollar davon sollen aus eigenen Nexo-Tokens bestehen.

... ouch       -> collectible-section

danke, aber so kann man sich an personen täuschen

Verdammt, hab ich leider nicht gesehen.

Hey, Gamers!

You can now enjoy Cometh Battle, a free-to-play tactical card game, through your Ledger Live app.
Build your deck according to your strategies and playstyle,
face thousands of players in intense 1vs1 space battles and tournaments.

All with clear signing, plus the industry-leading security that you’ve come to expect from Ledger.

Hey!

Du kannst jetzt Cometh Battle, ein kostenloses taktisches Kartenspiel, über deine Ledger Live-App spielen.
Stelle dein Deck nach deinen Strategien und deinem Spielstil zusammen,
Tritt gegen Tausende von Spielern in intensiven 1vs1-Weltraumschlachten und Turnieren an.

Do you all view Bitcointalk on you PC? I have tried to read thorugh the mobile phone, but it becomes an endless hortizontal scrolling.
Do you have any tips how to mingle on Bitcointalk with my phone?

sorry für die späte Rückmeldung...

Grund wird wohl der hier gewesen sein: https://medium.com/mycrypto/disclosure-key-generation-vulnerability-found-on-walletgenerator-net-potentially-malicious-3d8936485961

Ist https://www.bitaddress.org/ dann weiterhin save?

I tried to register but the bot seems asking for mobile number verification so I decided to quit.

13.200 $

Hat sich jemand das DUO Thema angeschaut bei Wirex und kann mal kurz erklären was das genau ist?

Für mich ist das kein ernsthaftes Investment, sondern lediglich ein bischen Spielerei.

Bin jetzt wieder auf das Thema aufmerksam geworden durch Haloxon  , @Real-Duke wie war das noch einmal in Kurzfassung, auf deinen PC hast du einen Trojaner installiert und der hat dann dein NAS gescannt durch vermutlich eine fixe Anbindung (Laufwerk im Explorer)? Nicht dein NAS wurde gehackt oder der Trojaner auf dem NAS installiert?

Mega wieder so eine coole Münze

Geschafft, bin auch wieder untenrum mit einem Röckchen bedeckt