Skip to content

v0.2.3
Compare
Choose a tag to compare
@shesek shesek released this 17 Mar 04:02
· 23 commits to master since this release
v0.2.3
This tag was signed with the committer’s verified signature. The key has expired.
shesek Nadav Ivgi
GPG key ID: 81F6104CD0F150FC
Expired
Learn about vigilant mode.
60aa672
This commit was signed with the committer’s verified signature. The key has expired.
shesek Nadav Ivgi
GPG key ID: 81F6104CD0F150FC
Expired
Learn about vigilant mode.

Changelog

  • New --prune-until <target> option to automatically prune the chain up to the given target (height, unix timestamp or YYYY-MM-DD formatted date)

    Require configuring bitcoind with prune=1 to allow manual pruning via the RPC.

  • New --no-wait-sync option to allow importing addresses without waiting for bitcoind to finish syncing first

    Useful for tracking wallets during the IBD of a pruned node, so transactions could be indexed before the blocks get pruned.

  • Fix compatibility with the upcoming v0.22 Bitcoin Core release (sparrowwallet/sparrow#67 (comment))

  • HTTP: Set the WWW-Authenticate header to make logging-in possible via web browsers

  • Implement an fd-based daemon readiness notification mechanism, enabled with FD_NOTIFY=<fd>

  • Fix whitepaper extractor

  • UX touchups for progress indicator, welcome banner and logs

  • Allow setting UNIX_LISTENER_MODE to control permissions for the unix socket notification listener

  • Allow setting NO_REQUIRE_ADDRESSES as an env variable

Breaking CLI changes:

  • The Electrum SOCKS5-based authentication needs to be explicitly enabled with --electrum-socks-auth,
    in addition to enabling the --auth-* options. By default, authentication will only be enabled for
    the HTTP API server.

Also see the v0.2.3 releases for bwt-electrum-plugin, libbwt, libbwt-nodejs and libbwt-jni.

Installation

Installation instructions are available on the README.

Verifying signatures

The releases are signed by Nadav Ivgi (@shesek). The public key can be verified on the PGP WoT, github, twitter, keybase, hacker news and this video presentation.

# Download (change x86_64-linux to your platform)
$ wget https://github.com/bwt-dev/bwt/releases/download/v0.2.3/bwt-0.2.3-x86_64-linux.tar.gz

# Fetch public key
$ gpg --keyserver keyserver.ubuntu.com --recv-keys FCF19B67866562F08A43AAD681F6104CD0F150FC

# Verify signature
$ wget -qO - https://github.com/bwt-dev/bwt/releases/download/v0.2.3/SHA256SUMS.asc \
  | gpg --decrypt - | grep ' bwt-0.2.3-x86_64-linux.tar.gz$' | sha256sum -c -

$ tar zxvf bwt-0.2.3-x86_64-linux.tar.gz
$ ./bwt-0.1.5-x86_64-linux/bwt --xpub <xpub> ...

The signature verification should show Good signature from "Nadav Ivgi <nadav@shesek.info>" ... Primary key fingerprint: FCF1 9B67 ... and bwt-0.2.3-x86_64-linux.tar.gz: OK.

Reproducible builds

The builds are fully reproducible.

You can verify the checksums against the v0.2.3 builds on Travis CI: https://travis-ci.org/github/bwt-dev/bwt/builds/763199070

See more details here.

Assets 13
Loading