From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-knots-announce@lists.linuxfoundation.org
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Bitcoin Knots 0.19.0.1.knots20200104 released
Date: Sun, 19 Jan 2020 17:04:35 +0000 [thread overview]
Message-ID: <202001191704.48707.luke@dashjr.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
Bitcoin Knots version 0.19.0.1.knots20200104 is now available from:
https://bitcoinknots.org/files/0.19.x/0.19.0.1.knots20200104/
This release includes new features, various bug fixes and performance
improvements, as well as updated translations.
Please report bugs using the issue tracker at GitHub:
https://github.com/bitcoinknots/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoinknots.org/list/announcements/join/
For the full release notes and change log, see:
https://github.com/bitcoinknots/bitcoin/blob/v0.19.0.1.knots20200104/doc/release-notes.md
New features of particular interest
===================================
- BIP157 (Neutrino) can be enabled to serve compact block filters to peers.
This requires both the `-blockfilterindex` and `-peercfilters` options
enabled, and can also be turned on in the GUI settings under the Network
tab.
- PSBT support has been experimentally expanded to include the new version and
proprietary fields, as well as easier usage from the GUI for watch-only
wallets.
- The Overview tab now has the ability to hide private information. This is
still an experimental feature, and suggestions for how the new "privacy
mode" should look can be made on the related Core PR:
https://github.com/bitcoin/bitcoin/pull/16432
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 1524 bytes --]
reply other threads:[~2020-01-19 17:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202001191704.48707.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=bitcoin-knots-announce@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox