Skip to content

Releases

v2.3.0-sec.2-java.4

Choose a tag to compare

@loki-notfound loki-notfound released this 11 Nov 00:00
v2.3.0-sec.2-java.4
859c6bf

The fourth release on the same core as v2.3.0-sec.2-java.1: https:// nodes work on Android,
with root certificates shipped in the library, and a daemon URI without a port works. No breaking
change.

Built from

The same zephyr-backports release set of 2026-11-07 as the previous releases, unchanged:

Tag Commit Tag subject
zephyr v2.3.0-sec.2 8c6a120256b4bd887d6e7167d929d76e3507e0e5 zephyr v2.3.0 + 30 security backports from Monero
zephyr-cpp v2.3.0-sec.1 3a2ee602ee28e6b7941b617ad4706349ad992641 zephyr-cpp master (4a99272f6d7a171cf6625016939094637459975a) + 4 security backports from monero-cpp

New build inputs: the root certificates of 2026-11-05 (Mozilla's list as curl publishes it,
https://curl.se/ca/cacert-2026-11-05.pem, 118 certificates, sha256
427c064216761a1e72a8b30f0d954d08cb6e4435a82091fb865afd20c8497285), and the build-layer patch
0006-openssl-android-environment (guide chapter 9).

Fixed

  • https:// nodes on Android. On the Android images this was measured on (the emulator, API 24
    and API 35) the native wallet could not verify any https:// node: OpenSSL ignored
    SSL_CERT_FILE and SSL_CERT_DIR in an app process, because it asked getauxval(AT_SECURE),
    which was set in the app process on both. The build now patches OpenSSL to compare the user and
    group ids, as on every platform without getauxval.
  • Correction: in v2.3.0-sec.2-java.1 to v2.3.0-sec.2-java.3 the guide, the README and
    these notes told Android apps to set SSL_CERT_FILE or SSL_CERT_DIR. On the emulator images
    named above that had no effect, so an https:// node could not be verified there; other
    devices were not measured. A node that seemed to work with its scheme written HTTPS:// was
    spoken in clear text (below). On the JVM the variables worked, and they still work when
    ZephyrTls is not used.
  • A daemon URI without a port: the core connected to port 0 and blocked for minutes without an
    error. An http or https URI without a port now gets the scheme's default port (80, 443).
  • ZephyrUtils.getVersion() returned "unknown" on Android: the AAR did not carry
    zephyr-java.properties. It does now.
  • A daemon URI whose scheme was not written in lower case (HTTPS://…) was spoken in clear text
    by the core; the scheme now reaches the core in lower case.

Added

  • zephyr.common.ZephyrTls: the root certificates the native wallet trusts for https:// nodes.
    By default the root certificates shipped in the library and nothing else, applied automatically
    on Android before the first https:// connection of a wallet (unless the environment already
    names SSL_CERT_FILE or SSL_CERT_DIR); the system store, the user's certificates, the app's
    own certificates and one exact file are options. Nothing changes on the desktop JVM unless the
    application calls ZephyrTls.
  • The shipped root certificates (zephyr/common/cacert.pem, Mozilla Public License 2.0), renewed
    with each release.
  • ZephyrTls.downloadCertificates, opt-in: fetches the current root certificates from curl.se
    (or another https source, optionally checked by sha256) for apps that want them before the
    next release. The library never calls it.

Changed

  • ZephyrWalletFull.getDaemonConnection() reports the URI with the default port when it was set
    without one.
  • When a call that needs the node fails with "Wallet is not connected to daemon" and the daemon
    URI is https://, the message adds ": the node is an https node; its certificate may not be
    trusted (see ZephyrTls and the user guide, chapter 6)". isConnectedToDaemon() is unchanged.
  • The JNI bridge checks for a pending Java exception after the calls that convert strings, so
    -Xcheck:jni reports no "JNI call made without checking exceptions" warnings any more.

Documentation

  • Guide chapter 6 "TLS to a node" rewritten (ZephyrTls, the shipped certificates, a private CA,
    the download, what cannot be done, the port); chapters 2, 8 and 9 and the README follow.

Tested

  • On the JVM (Linux) against a mainnet node behind a publicly signed certificate: a wallet
    without any ZephyrTls call connects through the host's store; with the shipped certificates
    applied it connects and reads the daemon height; with an empty CA file it does not connect,
    and sync() throws the error with the TLS hint; a URI without a port connects on 443; the
    download returns 118 certificates, a wrong checksum leaves the target untouched. Unit and
    integration tests under -Xcheck:jni: no warning.
  • On the Android emulator (x86_64), with this release's AAR in debug builds (CheckJNI on), on
    API 24 (with and without core library desugaring) and on API 35 with 16 KB pages: the checks of
    java.3, and https:// to a mainnet node without any setup and with a URI without a port
    (connected, a restored wallet synced over TLS, reopened from its bytes) and, on API 24 without
    desugaring and on API 35, with the scheme written HTTPS:// (connected, reported as
    https://); the system store alone (connected on API 35; on API 24 not, with the TLS hint);
    exactly one file (an empty file refused, ISRG Root X1 alone accepted); the download of the
    current root certificates. The ARM libraries have not yet run on hardware.

The dependency

Android: io.github.loki-notfound:zephyr-java-android:2.3.0-sec.2-java.4; the JVM:
io.github.loki-notfound:zephyr-java:2.3.0-sec.2-java.4. The repository line, the packaging
line and the dependencies are those of the earlier releases; guide chapter 6 says where they go.

Verification

gpg --import KEYS.asc
git verify-tag v2.3.0-sec.2-java.4
gpg --verify SHA256SUMS.asc && sha256sum -c SHA256SUMS

Not affiliated with ZephyrProtocol. An independent project. Report Zephyr vulnerabilities to the
ZephyrProtocol team, not here.

v2.3.0-sec.2-java.3

Choose a tag to compare

@loki-notfound loki-notfound released this 08 Nov 20:45
v2.3.0-sec.2-java.3
c0980ae

The third release on the same core as v2.3.0-sec.2-java.1: a fix in the JNI bridge for
debuggable Android apps, a clear error for the RPC classes on Android 7, and the Android
documentation. No breaking change.

Built from

The same zephyr-backports release set of 2026-11-07 as the previous releases, unchanged:

Tag Commit Tag subject
zephyr v2.3.0-sec.2 8c6a120256b4bd887d6e7167d929d76e3507e0e5 zephyr v2.3.0 + 30 security backports from Monero
zephyr-cpp v2.3.0-sec.1 3a2ee602ee28e6b7941b617ad4706349ad992641 zephyr-cpp master (4a99272f6d7a171cf6625016939094637459975a) + 4 security backports from monero-cpp

Fixed

  • The JNI bridge no longer releases null strings. Debuggable Android apps, in which ART's
    CheckJNI is always on, aborted when a wallet was created from a mnemonic or keys, or opened,
    with a connection without credentials: the bridge released the connection's null user name
    and password. This affected v2.3.0-sec.2-java.1 and v2.3.0-sec.2-java.2; release builds and
    the JVM (without -Xcheck:jni) were not affected. Every string release in the bridge now checks
    for null first, and the natives that read a path, a password or a byte array accept null
    like the others.
  • Memory leaks in four calls of the native bridge, ZephyrUtils.binaryToMap,
    ZephyrUtils.binaryBlocksToMap, ZephyrWalletFull.getSubaddresses and
    getAddressBookEntries, which never released the array passed to them, and in changePassword,
    which never released the two password strings.

Changed

  • The RPC classes (ZephyrDaemonRpc, ZephyrWalletRpc) report a missing java.time on
    Android 7.x (API 24 and 25) with a ZephyrError that names the remedy, Android 8.0 or core
    library desugaring in the app, on every request, instead of a bare NoClassDefFoundError.

Documentation

  • Guide chapter 6 (Android) completed: where the repository line goes, with the Groovy and
    version catalog forms; the RPC classes below API 26 and the desugaring lines; how to check which
    Jackson the app gets; ABI sizes and App Bundles; the INTERNET permission and clear text; Auto
    Backup and wallet data; logs; a first smoke test; where the libraries have run. The README and
    chapter 8 follow.

Tested

  • On the Android emulator (x86_64), with this release's AAR in debug builds (CheckJNI on), on
    API 24 and on API 35 with 16 KB pages: the offline wallet; a wallet restored from its mnemonic
    and synced against a mainnet node, then opened again from its bytes with a connection without
    credentials; ZephyrDaemonRpc on API 35, and on API 24 with core library desugaring; without
    desugaring, the new error on API 24. The ARM libraries have not yet run on hardware.

The dependency

Android: io.github.loki-notfound:zephyr-java-android:2.3.0-sec.2-java.3; the JVM:
io.github.loki-notfound:zephyr-java:2.3.0-sec.2-java.3. The repository line, the packaging
line and the dependencies are those of the earlier releases; guide chapter 6 says where they go.

Verification

gpg --import KEYS.asc
git verify-tag v2.3.0-sec.2-java.3
gpg --verify SHA256SUMS.asc && sha256sum -c SHA256SUMS

Not affiliated with ZephyrProtocol. An independent project. Report Zephyr vulnerabilities to the
ZephyrProtocol team, not here.

v2.3.0-sec.2-java.2

Choose a tag to compare

@loki-notfound loki-notfound released this 08 Nov 13:51
v2.3.0-sec.2-java.2
e5122fa

The second release on the same core as v2.3.0-sec.2-java.1: a fix for the Android x86_64
library, a helper for the asset of an output, and build changes. No breaking change.

Built from

The same zephyr-backports release set of 2026-11-07 as the previous release, unchanged:

Tag Commit Tag subject
zephyr v2.3.0-sec.2 8c6a120256b4bd887d6e7167d929d76e3507e0e5 zephyr v2.3.0 + 30 security backports from Monero
zephyr-cpp v2.3.0-sec.1 3a2ee602ee28e6b7941b617ad4706349ad992641 zephyr-cpp master (4a99272f6d7a171cf6625016939094637459975a) + 4 security backports from monero-cpp

Fixed

  • The x86_64 library in the AAR no longer needs an executable stack: every native library is
    now linked with -z noexecstack (the core's assembly files carry no non-executable-stack note,
    and NDK r18b's linker marked that library as needing one).

Added

  • ZephyrWallet.getOutputAssetType(output): the asset of an output from getOutputs(), which
    the core does not report, read from the output's transaction in the wallet's history. Guide
    chapter 8 has the rule and its limits.
  • Javadoc starting "Zephyr:" on checkTxKey, checkTxProof, ZephyrCheckTx.getReceivedAmount(),
    getOutputs() and ZephyrOutputWallet.getAssetType(): the amount of a payment check is 0 and
    an output carries no asset in the full wallet, why, and the workaround.

Build

  • The developer build (bin/build_libzephyr_java.sh) compiles for the generic CPU instead of the
    build machine's, so a library or a compiler cache made on one machine runs on another.
  • The Maven repository on Pages keeps every release: this release's site carries
    2.3.0-sec.2-java.1 next to 2.3.0-sec.2-java.2, and each maven-metadata.xml lists both.

The dependency

Android: io.github.loki-notfound:zephyr-java-android:2.3.0-sec.2-java.2; the JVM:
io.github.loki-notfound:zephyr-java:2.3.0-sec.2-java.2. The repository line, the packaging
line and the dependencies are those of the previous release, below.

Verification

gpg --import KEYS.asc
git verify-tag v2.3.0-sec.2-java.2
gpg --verify SHA256SUMS.asc && sha256sum -c SHA256SUMS

Not affiliated with ZephyrProtocol. An independent project. Report Zephyr vulnerabilities to the
ZephyrProtocol team, not here.

v2.3.0-sec.2-java.1

Choose a tag to compare

@loki-notfound loki-notfound released this 08 Nov 02:40
v2.3.0-sec.2-java.1
1d4cf76

The first release of zephyr-java: Java bindings for the Zephyr wallet core (zephyr-cpp over
Zephyr's wallet2), derived from monero-java at commit 53a54543 (2023-07-10), for Android (AAR)
and for desktop and server JVMs (JAR). The native core is linked statically into one library per
platform, libzephyr-java.so, which exports only its JNI entry points.

Built from

The core is built only from the tagged commits of the zephyr-backports forks:

Tag Commit Tag subject
zephyr v2.3.0-sec.2 8c6a120256b4bd887d6e7167d929d76e3507e0e5 zephyr v2.3.0 + 30 security backports from Monero
zephyr-cpp v2.3.0-sec.1 3a2ee602ee28e6b7941b617ad4706349ad992641 zephyr-cpp master (4a99272f6d7a171cf6625016939094637459975a) + 4 security backports from monero-cpp

These two tags belong to the zephyr-backports release set of 2026-11-07, which also names
zephyr-javascript v2.3.0-sec.1 (7b17a14280bd84ca783287f4640b3c744d25319f) and zephyr-wallet
v2.3.0-sec.1 (edef8c0ee281024de1a718aa6dce39bce75f3687); zephyr-java does not build those two.
The backports number each fork on its own: sec.<N> in this release's version is zephyr's tag
number, and the zephyr-cpp tag is named here and in manifest.json (core.zephyr-cpp.tag, next
to core.release_set and its members).

All tags are signed with the zephyr-backports release key
FB39 94F0 997C A6F0 43D7 2491 9EFF 03F5 27D2 40A1. A build against ZephyrProtocol's original
of the same release (zephyr v2.3.0 = 67c5f53b878fef41fb5e74c4382d5b7a2f37fd8a, zephyr-cpp
4a99272f6d7a171cf6625016939094637459975a) is expected to work as well.

Platforms

  • Android (io.github.loki-notfound:zephyr-java-android, AAR): minSdk 24; native libraries
    for arm64-v8a, armeabi-v7a and x86_64, 16 KB page aligned, stored uncompressed; consumer
    R8 rules included. armeabi-v7a needs a CPU with VFPv4. Built with NDK r18b through Zephyr's
    own contrib/depends. The AAR is built and checked (16 KB page alignment, uncompressed native
    libraries) in a throwaway consumer app; it has not yet run on a device or an emulator.
  • Linux (io.github.loki-notfound:zephyr-java, JAR): the native libraries for x86_64 and
    arm64 inside the JAR, loaded from it. Built in a Debian 12 container (glibc 2.36 or newer:
    Debian 12, Ubuntu 23.04 and later, RHEL 10); everything else is linked statically. The arm64
    library is built and checked, not yet run.
  • macOS and Windows: no packaged natives in this release.

The dependency

Android (Gradle, Kotlin DSL):

repositories {
    maven { url = uri("https://loki-notfound.github.io/myzephyr-java/maven") }
}

android {
    packaging { resources.excludes += "/META-INF/DEPENDENCIES" }
}

dependencies {
    implementation("io.github.loki-notfound:zephyr-java-android:2.3.0-sec.2-java.1")
}

The packaging line is required in every app: three of the Apache HTTP client's jars carry a
META-INF/DEPENDENCIES file, and the app's resource merge fails on the duplicates. Both the AAR
and the JAR bring the same three dependencies: jackson-core and jackson-databind 2.13.5 (the
last Jackson line for Android below API 26) and httpclient5 5.2.1. jeromq (only for
ZephyrWalletRpc's ZMQ listener) is optional and must be added by an application that uses it.
The JAR for Maven is io.github.loki-notfound:zephyr-java:2.3.0-sec.2-java.1; see the README's
"Coordinates".

Breaking changes against monero-java

zephyr-java mirrors monero-java's API; a port changes the following. Guide chapter 7, "Coming from
monero-java", has the details and the full renaming table.

  • Packages and names: monero.* → zephyr.*, common.* → zephyr.lib.*, classes
    Monero* → Zephyr*, the native library monero-java → zephyr-java.
  • toAtomicUnits / fromAtomicUnits: MoneroUtils.xmrToAtomicUnits(double) is
    ZephyrUtils.toAtomicUnits(double), MoneroUtils.atomicUnitsToXmr(BigInteger) is
    ZephyrUtils.fromAtomicUnits(BigInteger).
  • Balances are per asset: getBalance() returns a ZephyrBalance;
    getBalance(Integer accountIdx) returns Map<Integer, ZephyrBalance> keyed by subaddress;
    getBalance(String assetType, Integer accountIdx[, Integer subaddressIdx]) returns a
    BigInteger. The unlocked balance has the same shapes; ZephyrAccount and ZephyrSubaddress
    hold a ZephyrBalance. ZephyrBalance.equals treats an absent asset as zero.
  • The listener names the asset: onBalancesChanged(BigInteger, BigInteger) became
    onBalancesChanged(BigInteger, BigInteger, String assetType); the old method is final and
    deprecated, so a ported listener that overrides it does not compile. Outputs carry the asset in
    getAssetType().
  • Every send names a currency pair: a ZephyrTxConfig needs setSourceCurrency and
    setDestinationCurrency, a plain transfer included; without them the core fails with "Must
    specify source currency". The compiler does not find this one.
  • Addresses and constants: Zephyr's address prefixes (multi-byte varints) and network codes in
    ZephyrNetworkType; ZephyrUtils.RING_SIZE is 16. Bouncy Castle and commons-codec are no
    longer dependencies (own Keccak-256 and hex).
  • The RPC classes are a first pass: ZephyrWalletRpc serves the base coin and rejects the
    per-asset calls, reserve info and supply with a clear message.
  • Dependencies: slf4j-simple is no longer a runtime dependency (test scope only), and
    jeromq is optional.

New in zephyr-java: getReserveInfo() and getCirculatingSupply() on the wallet, ZephyrAssets
with the asset names, and the pricing record on daemon block headers.

Tested

The full wallet ran on mainnet against a node with real funds: create, open, sync, balances per
asset, transfers, a ZPH → ZRS conversion and sweeps (five transactions, verified on the node).
The pure test suite has 30 tests. Conversions other than ZPH → ZRS are not tested on mainnet.

Known limitations

Guide chapter 8, Known limitations, lists them with their
status. The ones a wallet app meets first: getOutputs() reports no asset; the asset of an
unconfirmed output notification is empty; checkTxKey returns amount 0; on Android, TLS to a node
needs the app's help (the native wallet does not use Android's certificate store).

Verification

The release tag and SHA256SUMS are signed with the maintainer key
31DA 39AB 43E0 CA67 F1F3 A661 BA2A FF22 DF8A 4A13; its public key is KEYS.asc in the
repository.

gpg --import KEYS.asc
git verify-tag v2.3.0-sec.2-java.1
gpg --verify SHA256SUMS.asc && sha256sum -c SHA256SUMS

The Maven repository and the site are the archive site-<version>.tar.gz, whose hash is in
SHA256SUMS; Pages serves its contents.

Build manifest

manifest.json among the release files records the zephyr-java commit and its
SOURCE_DATE_EPOCH, both core pins (tag, commit, URL), the build-layer patches, the toolchain
(compilers, NDK, CMake, JDK, Maven, Gradle and the Android Gradle plugin, the Linux container
image and its glibc), every depends package with its sha256, and the size and sha256 of every
release file. Every artifact is built twice in the same environment, and the hashes must match
before SHA256SUMS is signed. Guide chapter 9 explains how to repeat the build.

Not affiliated with ZephyrProtocol. An independent project. Report Zephyr vulnerabilities to the
ZephyrProtocol team, not here.