Skip to content

Releases

v0.15.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 19:55
Immutable release. Only release title and notes can be modified.
v0.15.0
1deb24c

[0.15.0] - 2026-11-15

Changed

  • Releases now prove their binaries before publishing anything. Both builds of each platform start as soon as the tag is validated, and every release image is packaged from those binaries before the release is approved. Public SDK crates, container images, and the GitHub Release are published only after both builds match. A build, reproduction, or packaging failure no longer leaves a published crate version without matching binaries. (#206)
  • Explorer views now keep per-height undo rows only for the reorg window, and ingest deletes older undo rows from an existing view store when it opens it, without a rebuild. New transparent-address delta and activity rows store each transaction id as 32 bytes instead of 64 hex characters, while rows already written keep reading. On a transparent-heavy fixture the two changes cut view storage by 41%. Rolling back to an earlier release requires rebuilding the Explorer views, because earlier releases read the rows this release writes with an empty transaction id. (#208)

Fixed

  • A transparent-address ranking build that trails Explorer views still rebuilding from canonical history now catches up and joins them, instead of falling further behind until replay reaches the tip, so address detail and activity return far sooner on read-limited storage. View replay waits for such a build while zinder_materialized_view_replay_waiting_for_ranking_build is 1, and stops waiting once the build, outside pauses it shares with replay, neither applies a page nor warms its cache further for 5 minutes. Spend resolution also issues fewer device reads, the prevout resolution metrics gain a cache label that names the walker, and zinder-ingest exports its canonical reader's RocksDB gauges under the canonical_secondary store role. (#209)

v0.14.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 11:56
Immutable release. Only release title and notes can be modified.
v0.14.0
1c0c673

[0.14.0] - 2026-11-15

Fixed

  • Explorer view replay and the transparent-address ranking build no longer slow to a few dozen blocks per minute when a deployment caps glibc malloc arenas, as MALLOC_ARENA_MAX=2 does; on a Mainnet-shaped fixture with that setting, replay ran about 24 times faster. Every service binary now allocates through jemalloc on Linux, including RocksDB's native allocations, so glibc malloc variables such as MALLOC_ARENA_MAX no longer apply. Remove them from the deployment and tune the allocator with MALLOC_CONF instead. Peak memory stayed within about 10% of glibc's on the same workload. (#199)
  • ExplorerQuery.TransactionDetail no longer fails with ARTIFACT_UNAVAILABLE for mined transactions with transparent outputs while the Explorer's transparent-outpoint spend view does not cover the response's chain epoch, such as during view replay or while the view and the wallet reader are a block apart at the tip. The response carries the transaction's facts, location, inputs, and outputs, omits every spent_by, and lists transparent_outputs.spent_by in freshness.unavailable with UNAVAILABLE_STALE; clients must treat an absent spent_by as unknown, not unspent, when that entry is present. The Cipherscan adapter reports that output state as spent: null. The zinder-wallet-serving-explorer image now starts zinder-explorer as soon as wallet serving answers when ZINDER_INGEST__EXPLORER_VIEWS is false, instead of after a 10-minute wait for view admission. zinder-query and zinder-compat-lightwalletd log wallet_serving_pair_publisher_refresh_failed at debug level, not as a warning, when a refresh only found its secondaries an epoch apart within the replica lag threshold. (#197)

v0.13.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 05:33
Immutable release. Only release title and notes can be modified.
v0.13.0
9106c3d

[0.13.0] - 2026-11-15

Added

  • Releases now publish the Explorer. The ghcr.io/zcashfoundation/zinder-explorer image can replace the locally built Explorer in the Compose overlay when it is pulled and started without a build, and the GNU/Linux binary archives include the zinder-explorer executable. For hosts that attach one volume to one container, such as Railway, the new ghcr.io/zcashfoundation/zinder-wallet-serving-explorer image runs wallet serving with Explorer views enabled on ingest. It serves ExplorerQuery on port 9068 and Explorer operations on port 9069, and starts the Explorer once wallet serving answers. If the Explorer exits, only the Explorer restarts, and wallet serving continues. The image healthcheck covers wallet serving alone, so monitor Explorer readiness on port 9069. ZINDER_EXPLORER__* variables reach only the Explorer. A volume built by zinder-wallet-serving can switch to this image: ingest then builds the Explorer views from canonical history. See the wallet-serving deployment runbook. (#165)

Fixed

  • zinder-projector no longer exits with canonical secondary did not reach the writer fence before the convergence deadline when a burst of blocks keeps the canonical writer committing ahead of it, which restarted every process in the single-volume wallet-serving runtime. It keeps applying the blocks its canonical secondary already holds while the writer is ahead, including right after a restart, each still authenticated against the writer's retained events, and when an attempt to reach the writer lasts projector.fence_convergence_timeout_seconds it logs canonical_secondary_behind_writer, reports replica_lagging, renews its canonical retention lease, and tries again. A ready projector also stays ready while its wallet trails the writer by any number of blocks, as long as it applies a block at least every 30 seconds and the trail lasts less than 2 minutes; it previously reported syncing whenever it trailed by two or more blocks. (#192)
  • Slow or abandoned TransparentAddressUnspentOutputs reads no longer stop zinder-query or zinder-compat-lightwalletd from publishing new chain epochs for every client. The read now sends outputs as it reads them, 1,024 at a time, reads storage only as fast as the client consumes, and stops when the client cancels or disconnects; the first outputs of a large address arrive after one page instead of after the whole set. A request may keep reading a serving pair for at most 30 seconds after a newer one replaces it and leaves retention. An unspent-output or full-block stream still reading past that limit ends with FAILED_PRECONDITION and CHAIN_EPOCH_PIN_UNAVAILABLE, which clients already treat as a signal to restart at a newer epoch. zinder_wallet_serving_pair_publisher_revoked_pairs_total and the wallet_serving_pair_reads_revoked warning report each such revocation. (#193)
  • Explorer view replay that resumes partway through history, as after a restart or upgrade, now warms its prevout cache from canonical history before it continues, instead of resolving most transparent spends through one canonical read at a time, and the canonical reads that remain run on up to 16 threads; the transparent-address ranking build does the same, and both log materialized_view_prevout_cache_warmed. On a store whose Explorer views were built without the transparent-address ranking, ingest now builds the ranking beside the view replay and joins it at the height the other views have reached, so explorer.transparent_address.activity_v2 and explorer.transparent_address.ranking_v1 are advertised long before replay reaches the tip; ingest logs transparent_address_ranking_joined_replay, and zinder_materialized_view_transparent_address_ranking_build_height and zinder_materialized_view_transparent_address_ranking_build_target_height report the build's progress. zinder_materialized_view_prevout_cache_outputs{cache} and zinder_materialized_view_prevout_cache_evicted_outputs_total{cache} report prevout cache use. Explorer view files now compress with ZSTD, which used about a third less disk than the previous Snappy default on a transparent-dense fixture; existing view stores open in place and shrink as compaction rewrites their files. (#194)

v0.12.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 23:05
Immutable release. Only release title and notes can be modified.
v0.12.0
28e96b0

[0.12.0] - 2026-11-14

Fixed

  • zinder-projector no longer reports syncing with lag_blocks: 1 for a moment after every block: a ready projector within one block of the canonical tip stays ready while it applies the block, and reports syncing only if 30 seconds pass without it applying a block or it trails by more than one block. zinder-query now exits promptly on SIGTERM even while wallets hold ChainEvents or MempoolEvents streams open: it ends every open stream with UNAVAILABLE and readiness cause shutting_down, and stops waiting for in-flight calls after 10 seconds, so it stops within the wallet-serving supervisor's 20-second grace window. (#182)
  • ExplorerQuery.TransparentAddressActivity no longer fails with FAILED_PRECONDITION while the transparent-address ranking is ahead of the requested chain epoch, which happened for most of every block interval. Address summaries, ranking coverage, and activity rows now describe the epoch's visible tip. A read still fails with FAILED_PRECONDITION when the ranking holds a different block than the epoch, including while it trails the epoch on a replaced branch, or when it would need to rewind more than 1,000 blocks. The Cipherscan adapter no longer marks /api/address/:address degraded only because the Explorer views lead the pinned epoch; it does so when ranking coverage stops short of the epoch's tip. (#183)
  • Explorer view replay and the transparent-address ranking build no longer re-read the producing block for each transparent spend of an output they already replayed, which made transparent-heavy history such as early Mainnet replay at a few hundred blocks per minute; they keep up to about 375 MB of unspent outputs in memory while they walk history and release it at the tip or under memory pressure. Explorer view replay, the ranking build, and historical view backfills now also pause while the volume holding storage.path has less available space than the new ingest.explorer_views_min_free_bytes (ZINDER_INGEST__EXPLORER_VIEWS_MIN_FREE_BYTES, default 10 GiB, 0 disables), logging materialized_view_replay_volume_space_low, and resume on their own once a tenth more is available; canonical ingest and wallet serving keep running. Existing Explorer view stores resume in place. (#184)

v0.11.1

Choose a tag to compare

@github-actions github-actions released this 14 Nov 17:37
Immutable release. Only release title and notes can be modified.
v0.11.1
06c3741

[0.11.1] - 2026-11-14

Fixed

  • The zinder-canonical-runtime and zinder-wallet-serving images now carry /usr/local/lib/zinder as a traversable directory. In 0.11.0 the image build gave that directory mode 0644, which stopped the release from publishing images, binary archives, and a GitHub Release for that version. Zinder 0.11.0 exists only as the zinder-core, zinder-proto, and zinder-client crates; deploy 0.11.1 instead, which contains every 0.11.0 change. (#174)

v0.10.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 09:17
Immutable release. Only release title and notes can be modified.
v0.10.0
7ef15d8

[0.10.0] - 2026-11-13

Added

  • Native WalletQuery.TransparentOutpointSpendStatus reports, for 1 to 1,024 transparent outpoints read at one chain epoch, whether each output is unspent, spent (with the spending transaction, input index, and block), or not found. It replaces TransparentSpendsByOutpoint and TransparentUnspentOutputsByOutpoint with one call, is served from the wallet projection without the Explorer views, and is advertised as wallet.read.transparent_outpoint_spend_status_v1. In zinder-client, call ChainSnapshot::transparent_outpoint_spend_status, which splits larger batches at one pinned epoch. A request with no outpoints or more than 1,024 fails with INVALID_ARGUMENT and the new TRANSPARENT_OUTPOINT_COUNT_OUT_OF_RANGE reason. On a store whose history starts after a checkpoint, a request that misses any outpoint fails with FAILED_PRECONDITION and CANONICAL_HISTORY_UNAVAILABLE instead of reporting it not found. The request reveals the outpoints a wallet tracks and, through them, the addresses that own them. (#143)
  • Broadcast results now distinguish transactions rejected for an unsupported transaction version (UnsupportedTransactionVersion, wire value 6) from transactions that exceed the per-block action limit (ExceedsBlockActionLimit, wire value 7), where both previously appeared as Unknown. zinder-client now decodes unspecified and unrecognized rejection reasons as Unknown instead of failing with MalformedResponse. Earlier zinder-client releases reject the new values, so release the client and update consumer pins before or together with the server. (#134)
  • Ingest now decodes blocks after NU7 activates (branch ID 0x77190ad9). Zinder 0.9.0 and earlier stop at the first NU7 block, so upgrade Zinder before the node serves NU7 blocks. (#136)

Changed

  • Native WalletQuery.CompactBlocksInRange now sends the chain view once, as the first stream message, followed by bare compact blocks, instead of repeating the full chain view on every block. CompactBlocksInRangeChunk is now a oneof body with header and item. zinder-client keeps the same compact_blocks_in_range API and rejects a stream whose header is missing, repeated, or out of order with MalformedResponse. Upgrade notes: the native contract revision is now 7. Native query and ingest must run the same revision, so upgrade zinder-ingest and zinder-query together: zinder-query admits only an ingest at its own revision and fails at startup against a revision 6 zinder-ingest. No upgrade order is safe for native clients: a client built before this release fails on the first CompactBlocksInRange message from a new server, and this zinder-client refuses servers below revision 7. Release consumers such as Zally-based wallets on this zinder-client, then cut the Zinder services and those consumers over together. Raw gRPC consumers must read the leading header and take blocks from body.item. (#142)
  • Document the GetLightdInfo and GetLatestBlock identity contracts for lightwalletd compatibility, and compare tip-dependent fields in live parity tests only at equal tips. (#135)
  • Raw transaction bytes with trailing data now fail with RawTransactionParseFailed instead of being accepted for v1 to v4 transactions. Cipherscan avgBlockTimeSecs, the mining blockTime fallback, and the network-activity fallback interval now follow the target spacing at the block height (25 s from NU7) instead of a fixed 75 s. (#136)
  • Wallet build cold validation reads the flushed store back once per family and compares it with the construction digest instead of re-sorting the address families, which shortens large builds. The wallet build report replaces the two cold-validation sort durations with per-family scan durations, and the storage benchmark report format moves to version 4. (#138)

Removed

  • Native WalletQuery now serves only the transparent reads its consumers need: TransparentAddressUnspentOutputs, ascending TransparentAddressTxIdsInRange, and TransparentOutpointSpendStatus. Removed, together with their capabilities and zinder-client methods: TransparentAddressBalance, TransparentOutputsByOutpoint, TransparentSpendsByOutpoint and TransparentUnspentOutputsByOutpoint (replaced by TransparentOutpointSpendStatus), the three transparent mempool lookups and their IngestControl methods, TransparentUtxoSetSummary, ExplorerQuery.UtxoSetSummary, and the descending history flag. The lightwalletd-compatible GetTaddressBalance is unchanged. Wallet and ingest ServerInfo and readiness no longer report materialized_view_preset; Explorer view identities are reported by ExplorerServerInfo. The zinder_materialized_view_workload_info metric is removed and zinder_materialized_view_identity_info loses its preset label. Upgrade notes: the native contract revision is now 8. Native query and ingest must run the same revision, so upgrade zinder-ingest and zinder-query together: zinder-query admits only an ingest at its own revision and fails at startup against a revision 7 zinder-ingest. No upgrade order is safe for native clients: a client built before this release receives UNIMPLEMENTED from a removed method on a new server, and this zinder-client refuses servers below revision 8. Release consumers such as Zally-based wallets on this zinder-client, then cut the Zinder services and those consumers over together. Explorer view stores built by earlier releases are refused at startup and must be rebuilt on a fresh materialized-view path (see the deploying-on-a-VM runbook). A client built before this release that sends descending = true now receives ascending results. Zallet's Zinder backend uses one removed item, the descending history flag: delete descending: false in backends/zinder/src/chain.rs and the test assertion on it. Its other zinder-client and zinder-core imports still exist. That was checked against the API surface, not by compiling Zallet, and upgrading it from =0.6.0 also crosses every other breaking change since that release. (#143)

Fixed

  • Native WalletQuery.Transaction and zinder-client now report a transaction as not found only when the absence is proven, so a wallet can safely treat TxStatus::NotFound as "never mined at this epoch". A proven absence is gRPC NOT_FOUND with the new reason TRANSACTION_NOT_FOUND, whose metadata names the epoch it covers, the covered heights, and whether the live mempool was searched. A pinned lookup (at_epoch_id, or a ChainSnapshot) covers that epoch's canonical chain only; an unpinned lookup also covers the writer's mempool at the same epoch. Storage faults, a missing or unserved epoch, and a block outside the best chain are now errors rather than NotFound. A store whose history starts after a checkpoint cannot prove an absence: it answers a miss with the new CANONICAL_HISTORY_UNAVAILABLE reason (FAILED_PRECONDITION, reported as IndexerError::CanonicalHistoryUnavailable with the first retained height), while an unpinned lookup still reports a pending transaction as in the mempool. On such a store, lightwalletd-compatible GetTransaction now fails a miss with FAILED_PRECONDITION instead of NOT_FOUND, and is_in_mempool fails with CanonicalHistoryUnavailable instead of returning false for a transaction that is neither pending nor mined above the floor. When the node reports a transaction mined in any block other than the tip the live mempool generation serves, ingest now ends that generation instead of removing the transaction, so live mempool reads return UNAVAILABLE until the next snapshot is certified rather than briefly reporting the transaction as absent from both the chain and the mempool. The mempool half of an unpinned absence remains best effort around reorgs; use a pinned lookup (at_epoch_id or a ChainSnapshot) for payment decisions. Upgrade notes: the native contract revision is now 6, and native query and ingest must run the same revision. The new client reports a NOT_FOUND from an older server as IndexerError::TransactionAbsenceUnverified instead of NotFound, so upgrade servers before relying on absences; an older client keeps reading every NOT_FOUND as NotFound. (#105)
  • The release verification commands in the deployment and release runbooks now name the ZcashFoundation/zinder repository. Releases from v0.8.0 onward are signed by https://github.com/ZcashFoundation/zinder/.github/workflows/release.yml and publish images under ghcr.io/zcashfoundation/, so the previously documented gustavovalverde identity and image path rejected genuine releases. (#126)
  • Compact-blocks GetBlockRange now omits transactions that the requested pool types leave with no data, such as a transparent-only coinbase under the default shielded selection, so range responses match lightwalletd. Remaining transactions keep their CompactTx.index. (#137)
  • RemoteChainIndex::mempool_events now fails the stream with MalformedResponse, before yielding the event, when a mempool event repeats or decreases event_sequence, reuses a cursor, or carries an empty cursor. Cursor retention is bounded to 65,536 cursors and 8 MiB per stream, matching chain events. (#141)
  • The lightwalletd-compatible service now matches lightwalletd ...
Read more

v0.9.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 13:21
Immutable release. Only release title and notes can be modified.
v0.9.0
e86dd1a

[0.9.0] - 2026-11-12

Added

  • Each release now publishes two more multi-architecture images for hosts that attach one volume to one container. ghcr.io/zcashfoundation/zinder-wallet-serving runs ingest, projector, and native query as supervised processes and omits lightwalletd compatibility. ghcr.io/zcashfoundation/zinder-canonical-runtime is the ingest-only diagnostic or canary runtime. Both carry the same provenance, SBOM, and signature evidence as the four runtime images, and neither is the complete supported topology. (#128)

Removed

  • deploy/Dockerfile.wallet-serving, deploy/Dockerfile.railway-nocache, railway.toml, deploy/railway.canonical-runtime.toml, and deploy/railway.wallet-serving-runtime.toml are removed, along with the RAILWAY_DOCKER_TARGET_STAGE build argument. Pull the published zinder-wallet-serving or zinder-canonical-runtime image instead, or build the target of that name from deploy/Dockerfile. Railway services must switch from a repository build to a Docker image source, then set the healthcheck path, healthcheck timeout, restart policy, and drain window in the service settings as the deployment runbooks describe. (#128)

v0.9.0-rc.1

v0.9.0-rc.1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 12 Nov 08:21
Immutable release. Only release title and notes can be modified.
v0.9.0-rc.1
9d32051

[0.9.0-rc.1] - 2026-11-12

Added

  • Each release now publishes two more multi-architecture images for hosts that attach one volume to one container. ghcr.io/zcashfoundation/zinder-wallet-serving runs ingest, projector, and native query as supervised processes and omits lightwalletd compatibility. ghcr.io/zcashfoundation/zinder-canonical-runtime is the ingest-only diagnostic or canary runtime. Both carry the same provenance, SBOM, and signature evidence as the four runtime images, and neither is the complete supported topology. (#128)

Removed

  • deploy/Dockerfile.wallet-serving, deploy/Dockerfile.railway-nocache, railway.toml, deploy/railway.canonical-runtime.toml, and deploy/railway.wallet-serving-runtime.toml are removed, along with the RAILWAY_DOCKER_TARGET_STAGE build argument. Pull the published zinder-wallet-serving or zinder-canonical-runtime image instead, or build the target of that name from deploy/Dockerfile. Railway services must switch from a repository build to a Docker image source, then set the healthcheck path, healthcheck timeout, restart policy, and drain window in the service settings as the deployment runbooks describe. (#128)

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 19:29
Immutable release. Only release title and notes can be modified.
v0.8.0
4b05008

[0.8.0] - 2026-11-11

Removed

  • Ingest no longer accepts the configuration keys of its removed batch catch-up and tip-follow paths. Remove ingest.construction.canonical_batch_max_blocks, canonical_batch_max_artifact_bytes, canonical_batch_max_estimated_write_bytes, canonical_batch_min_blocks_before_estimated_write_close, commit_reassembly_max_queued_artifact_bytes, flush_interval_epochs, ingest.run_overrides.allow_reorg_window_settlement, and the ingest storage.secondary_path key, along with their ZINDER_INGEST__* environment variables, before upgrading: ingest refuses to start while any of them is set. The zinder-ingest verify-canonical-replay subcommand is removed; it could not open a canonical store written by the release ingest path. The storage benchmark drops its canonical-store range replay scenario and Compose profile, and the ZinderStoreReadP95High alert and its dashboard panel are removed because no release runtime emits the store read metrics they watched. Explorer methods that need canonical storage keep returning FAILED_PRECONDITION with DEPENDENCY_NOT_CONFIGURED, as they did before; the Cipherscan compatibility matrix now marks the routes that depend on them. (#115)

Fixed

  • Lightwalletd compatibility now refuses to start when its canonical secondary disagrees with the ingest writer fence on the visible block count, which it previously accepted. Native query now fails closed on a writer fence that diverges from its secondary instead of retrying it as replica lag until its attempts run out. Projector, native query, and lightwalletd compatibility now apply the same fence rules. (#116)
  • Wallet reads served by zinder-query and zinder-compat-lightwalletd now record zinder_query_request_* metrics. Before, only operations proxied through the native adapter produced samples, so the ZinderWalletQueryP95High alert and the overview dashboard missed most wallet traffic. Expect new samples for every wallet read, including reads the serving store cannot answer. (#117)
  • Explorer /readyz now reports schema_mismatch or storage_unavailable while its materialized-view catch-up fails, instead of staying ready. Ingest now stays upstream_not_ready until its Zebra health probe recovers; the follow loop no longer clears that cause, and WriterStatus reports the probe observation during construction and source recovery. When [node.health] is configured, ingest reports starting until the first successful probe instead of ready. Ingest, Explorer, and the Cipherscan adapter now report shutting_down as soon as termination is requested. (#118)
  • A materialized-view rebuild that resumes without chain-event cursors after a reorg now reverts rows from the replaced chain before rebuilding, instead of keeping them. The transparent address activity index and the address ranking undo journals now write the same bytes regardless of hash-map order or batch size, so replaying the same chain produces identical materialized-view stores. (#119)
  • Native CompactBlocksInRange and lightwalletd GetBlockRange now return NOT_FOUND with reason ARTIFACT_UNAVAILABLE for a range that reaches outside stored history, such as height 0 or a height below the retained floor, instead of UNAVAILABLE. A missing row inside retained history still reports a storage error, and GetBlockRange above the visible tip still returns OUT_OF_RANGE. (#122)
  • Subtree-root reads on a checkpointed store now return NOT_FOUND with reason ARTIFACT_UNAVAILABLE for a root that completed below the retained history and was never loaded, instead of UNAVAILABLE. A missing root the store loaded, including any root of a store built with the complete subtree-root prefix, still reports a storage error. (#123)

v0.6.0

Choose a tag to compare

@github-actions github-actions released this 10 Aug 18:51
Immutable release. Only release title and notes can be modified.
v0.6.0
9b9e704

[0.6.0] - 2026-08-10

Changed

  • Lightwalletd-compatible deployments now advertise transparent-address support only when their serving data can answer those requests. Startup rejects configurations that lack a transparent wallet projection or retained transaction bytes. (#71)
  • Document the production Testnet Zebra readiness calibration that keeps ordinary block gaps available while peer, sync, lag, and stale-tip failures remain fail-closed. (#73)

Fixed

  • Stale fixed-view mempool epochs now reach the typed view-expiration path so wallet consumers can reacquire the view without treating expected chain rotation as service unavailability. (#69)
  • Secondary query and projection processes no longer create thousands of short-lived storage threads per second while following the chain. (#72)