Java Native Interface bindings for Bitcoin Wallet Tracker, a lightweight personal indexer for bitcoin wallets.

libbwt-jni allows to programmatically manage bwt's Electrum RPC and HTTP API servers. It can be used as a compatibility layer for easily upgrading Electrum-backed wallets to support a Bitcoin Core full node backend (by running the Electrum server in the wallet), or for shipping software that integrates bwt's HTTP API as an all-in-one package.

Support development: ⛓️ on-chain or ⚡ lightning via BTCPay

• Usage
• Installation
  • AAR (for Android/Kotlin)
  • Manual (non-Android or without Kotlin)
  • Electrum only
  • Verifying the signature
• Building from source
• Reproducible builds
• License

Also see: bwt, libbwt and libbwt-nodejs.

With the higher-level BwtDaemon implemented in Kotlin:

import dev.bwt.libbwt.daemon.* import dev.bwt.libbwt.BwtException val bwt = BwtDaemon(BwtConfig( bitcoindUrl = "http://127.0.0.1:8332", bitcoindAuth = "satoshi:otomakan", descriptors = arrayOf("wpkh(xpub66../0/*)", "wpkh(xpub66../1/*)"), xpubs = arrayOf("xpub11...", "ypub22...", "zpub33..."), rescanSince = 1510160280, // unix timestamp electrumAddr = "127.0.0.1:0", // bind on any available port )) try { // start() will block the current thread and won't return until the daemon is stopped. bwt.start(object : ProgressNotifier { override fun onBooting() { // Called after the configuration is validated, right before starting up println("Daemon booting up...") } override fun onSyncProgress(progress: Float, tip: Date) { println("Initial block download in progress... ($progress done, synced up to $tip)") } override fun onScanProgress(progress: Float, eta: Int) { println("Wallet rescanning in progress... ($progress done, ETA $eta seconds)") } override fun onReady() { println("Daemon ready, Electrum server bound on ${bwt.electrumAddr}") bwt.shutdown() } }) } catch (e: BwtException) { println("Daemon startup failed: $e") }

Alternatively, you may use the lower-level NativeBwtDaemon directly, which does not require Kotlin. Refer to the BwtDaemon implementation for example usage.

For the full list of available configuration options, refer to the libbwt C FFI docs.

The API servers are unauthenticated by default, but authentication can be enabled.

Note that if you call shutdown() while bitcoind is importing/rescanning addresses, the daemon will not stop immediately but will be marked for later termination.

Pre-built signed & deterministic library files are available for Linux, Mac, Windows, ARMv7/8 and Android.

⚠️ The pre-built libraries are meant to make it easier to get started. If you're integrating bwt into real-world software, building from source is highly recommended.

The AAR library is available for download from the releases page.

Installation instructions for AAR are available here.

If you're not developing for Android, or if you are but would like to avoid using the AAR or Kotlin, you can use the JNI libraries directly.

1. Download the JNI library for you platform(s) from the releases page and copy it into your jniLibs directory.

2. Copy the dev.bwt.libbwt source code into your project. You may omit BwtDaemon.kt and use NativeBwtDaemon directly instead.

3. If you choose to use BwtDaemon, you'll need to have com.google.gson installed.

The pre-built libraries are also available for download as an electrum_only variant, which doesn't include the HTTP API server. It is roughly 33% smaller and comes with less dependencies.

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 (bottom of slide).

# Download (change x86_64-linux to your platform) $ wget https://github.com/bwt-dev/libbwt-jni/releases/download/v0.2.4/libbwt-jni-0.2.4-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/libbwt-jni/releases/download/v0.2.4/SHA256SUMS.asc \ | gpg --decrypt - | grep x86_64-linux.tar.gz | sha256sum -c -

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

Manually build the JNI library for a single platform (requires Rust):

$ git clone https://github.com/bwt-dev/libbwt-jni && cd libbwt-jni $ git checkout <tag> $ git verify-commit HEAD $ git submodule update --init $ cargo build --release --target <platform>

The library file will be available in target/<platform>/release, named libbwt_jni.so for Linux/Android/ARM, libbwt_jni.dylib for OSX, or bwt_jni.dll for Windows.

To build the electrum_only variant, set --no-default-features --features electrum.

Building for Android targets requires NDK to be installed in your PATH.

To build the AAR, first build the JNI libraries for all android platforms, place them under library/src/main/jniLibs, then run ./gradlew build (or use the Docker builder below).

The JNI builds for all supported platforms and the AAR library for Android can be reproduced in a Docker container environment as follows:

$ git clone https://github.com/bwt-dev/libbwt-jni && cd libbwt-jni $ git checkout <tag> $ git verify-commit HEAD $ git submodule update --init # JNI libraries for Linux, Windows, ARMv7 and ARMv8 $ docker build -t bwt-builder - < bwt/scripts/builder.Dockerfile $ docker run -it --rm -u `id -u` -v `pwd`:/usr/src/libbwt-jni -w /usr/src/libbwt-jni \ --entrypoint scripts/build.sh bwt-builder # JNI libraries for Mac OSX (cross-compiled via osxcross) $ docker build -t bwt-builder-osx - < bwt/scripts/builder-osx.Dockerfile $ docker run -it --rm -u `id -u` -v `pwd`:/usr/src/libbwt-jni -w /usr/src/libbwt-jni \ --entrypoint scripts/build.sh bwt-builder-osx # JNI libraries + AAR for Android platforms (x86, x86_64, arm32v7, arm64v8) $ docker build -t bwt-builder-android - < bwt/scripts/builder-android.Dockerfile $ docker run -it --rm -u `id -u` -v `pwd`:/usr/src/libbwt-jni -w /usr/src/libbwt-jni \ --entrypoint scripts/build-android.sh bwt-builder-android $ sha256sum dist/*.tar.gz

You may set -e TARGETS=... to a comma separated list of the platforms to build. The available platforms are: x86_64-linux, x86_64-osx, x86_64-windows, arm32v7-linux, arm64v8-linux, arm32v7-android, arm64v8-android, i686-android and x86_64-android.

Both variants will be built by default. To build the electrum_only variant only, set -e ELECTRUM_ONLY_ONLY=1.

The builds are reproduced on Travis CI using the code from GitHub. The SHA256 checksums are available under the "Reproducible builds" stage.

MIT