Zakura is a Zcash full node: a program that downloads and verifies the whole blockchain, like Zebra. Its own README says it is written in Rust and forked from Zebra, and the official zcashd repository names it as a place to move to after zcashd's end of support. This article summarises what the project says about itself and marks every claim we could not check.

Status as of October 12, 2026

Sources are Zakura's website (home, About, Download and Engineering pages), its GitHub README, the official zcashd repository notice and the zcashd end-of-life page, all read on October 12, 2026. We did not install or run Zakura. Speed and feature statements are the project's own, not our measurements.

What Zakura is

Zakura's site describes it as "a consensus-compatible Zcash full node, built for scale," and lists faster sync, native block pruning, a zcashd compatibility mode and an experimental peer-to-peer layer. The GitHub README says it is "forked from Zebra" and dual-licensed under MIT and Apache 2.0 (some crates MIT-only). A full node verifies every block and transaction itself; it is not a wallet, and a light wallet connects to a server instead (see light wallet).

Who builds it

The About page says Zakura is developed by "veteran protocol engineers from the Zcash, Cosmos, and Celestia ecosystems," as a collaboration between Valar Group and Project Tachyon, with Sean Bowe and Dev Ojha listed as maintainers. It does not say how the project is funded and does not mention Zebra, the Zcash Foundation or Zodl. For what Project Tachyon is, see our Tachyon explainer.

How it relates to Zebra and zcashd

  • zcashd was the original node software. It reached its final end-of-support halt on July 18, 2026, and the zcashd repository names Zebra and Zakura as the node implementations to move to (for what the shutdown meant for old wallet setups, see wallet troubleshooting).
  • Zebra is the Zcash Foundation's Rust node, and the one our node guide covers with commands, ports and hardware from its documentation.
  • Zakura started as a fork of Zebra. A fork is its own project: it can diverge in features, release schedule and support.

Both are consensus nodes. Both need the same care around network upgrades: a node that does not follow an upgrade stops following the chain (see the upgrade tracker).

What the project says about speed and size

  • Syncing the chain is "nearly 5ร— faster than other full nodes."
  • Pruned nodes can bootstrap in "2 minutes from the snapshots our team publishes."
  • Its engineering page reports, for an 80-node stressnet test of 25-second blocks, a measured 3.43 percent orphan rate while mining full 2 MB blocks.

These are Zakura's statements. The pages we read do not give the hardware, the baseline node, the date or the method for the first two, so we cannot confirm or reject them. The stressnet figure concerns the 25-second block time planned for NU7, which is still a plan (see NU7 explained).

How to get it, and what the project warns about

The Download page lists four routes: installing from crates.io with cargo (marked recommended), an interactive installer script, prebuilt release binaries and a source tarball on GitHub, and an official Docker image (zakuracore/zakura). It also says:

  • Each release's checksum file is signed with minisign, and every release asset carries a GitHub artifact attestation. Verify downloads with them.
  • Only crates.io, the GitHub releases page and Docker Hub are official channels; binaries from anywhere else are not the project's.
  • "The Docker images are not yet signed."

Piping a script from the internet into a shell runs it with your user's rights. The cargo route and verified archives give you more control. Whatever you choose, run a node on a machine you can afford to rebuild, and do not type your wallet's recovery phrase into node software: a consensus node itself does not need it.

Version note

The Download page lists release 1.6.0 dated October 1, 2026. The README's install example refers to a v1.6.1 tag. We did not resolve the difference; check the releases page before you install.

What we could not verify

  • Speed and pruning claims. Not measured by us; no method stated on the pages we read.
  • Supported operating systems and hardware needs. The README and Download page give no formal list or figures.
  • The zcashd compatibility mode. Described on the site, not tested.
  • Funding and governance. The About page does not state them.
  • Which release is current. 1.6.0 on the site, v1.6.1 in the README example.
  • Snapshots. The site links to them; we did not read or check how they are built or verified.

Sources

Zakura website, About, Download, Engineering, Zakura on GitHub, the zcashd repository notice and the zcashd end-of-life page.