Go to file
Marek 0b8e73206f
change(docs): Update User Docs (#6733)
* Move releases info to `Building Zebra`

* Move Zebra use-cases to `Using Zebra`

* Point the links in Zebra use-cases to docs

* Move the contents of `Release Candidates`

* Refactor the `System Requirements` link

* Update the syncing times

* Update notes on performance

* Move data usage to `System Requirements`

* Remove "building Zebra" from lightwalletd docs

I think we can assume people will follow the previous parts of the docs
for how to build Zebra.

* Move lightwalletd details from `README.md` to docs

`README.md` already mentions lightwalletd from the `Using Zebra`
section, and refers the reader to the docs where the details were moved
and refactored.

* Mention `lightwalletd` and mining in Running Zebra

* Move Troubleshooting to its own file

* Move "Improving Performance" to its own file

* Move instructions for ARM to "Installing Zebra"

* Reword the Testnet sync duration description

Co-authored-by: Pili Guerra <mpguerra@users.noreply.github.com>

* Move "Improving Performance" to "Troubleshooting"

* Remove the Testnet unreliability caveat

---------

Co-authored-by: Pili Guerra <mpguerra@users.noreply.github.com>
2023-05-23 13:18:57 +00:00
.cargo fix(clippy): Silence future-incompat warnings until we upgrade Abscissa (#6024) 2023-01-24 16:27:56 +00:00
.github build(deps): bump Swatinem/rust-cache from 2.3.0 to 2.4.0 (#6741) 2023-05-22 21:40:22 +00:00
book change(docs): Update User Docs (#6733) 2023-05-23 13:18:57 +00:00
docker change(ci): Generate testnet checkpoints in CI (#6581) 2023-05-03 23:14:22 +00:00
grafana change(state): Add block channel metrics, in preparation for block fork metrics (#5327) 2022-10-20 20:02:58 +00:00
tower-batch build(deps): bump pin-project from 1.0.12 to 1.1.0 (#6677) 2023-05-16 21:07:06 +00:00
tower-fallback build(deps): bump pin-project from 1.0.12 to 1.1.0 (#6677) 2023-05-16 21:07:06 +00:00
zebra-chain Delete outdated `TODOs` refering to closed issues (#6732) 2023-05-23 03:33:14 +00:00
zebra-consensus Delete outdated `TODOs` refering to closed issues (#6732) 2023-05-23 03:33:14 +00:00
zebra-network Delete outdated `TODOs` refering to closed issues (#6732) 2023-05-23 03:33:14 +00:00
zebra-node-services build(deps): bump reqwest from 0.11.17 to 0.11.18 (#6707) 2023-05-17 22:09:35 +00:00
zebra-rpc Delete outdated `TODOs` refering to closed issues (#6732) 2023-05-23 03:33:14 +00:00
zebra-script v1.0.0-rc.8 release (#6632) 2023-05-11 22:15:12 +00:00
zebra-state Delete outdated `TODOs` refering to closed issues (#6732) 2023-05-23 03:33:14 +00:00
zebra-test v1.0.0-rc.8 release (#6632) 2023-05-11 22:15:12 +00:00
zebra-utils build(deps): bump reqwest from 0.11.17 to 0.11.18 (#6707) 2023-05-17 22:09:35 +00:00
zebrad build(deps): bump vergen from 8.1.3 to 8.2.0 (#6742) 2023-05-23 00:43:48 +00:00
.codespellrc build(deps): Bump `zcash_proofs` to 0.8.0 (#5481) 2022-10-28 06:58:02 +00:00
.dockerignore fix(build): avoid docker cache contamination and invalidation (#4254) 2022-05-03 10:13:28 -04:00
.gitattributes Show `Cargo.lock` files in the github diff view (#6249) 2023-02-28 20:06:32 +00:00
.gitignore fix: improve file and directories to be ignored by git and Docker (#3399) 2022-01-26 06:22:51 +00:00
CHANGELOG.md v1.0.0-rc.8 release (#6632) 2023-05-11 22:15:12 +00:00
CODE_OF_CONDUCT.md CODE_OF_CONDUCT.md (#1097) 2021-03-25 10:54:08 +01:00
CONTRIBUTING.md docs: fix typo (#3877) 2022-03-22 22:01:35 -04:00
Cargo.lock build(deps): bump vergen from 8.1.3 to 8.2.0 (#6742) 2023-05-23 00:43:48 +00:00
Cargo.toml Temporarily delete unused zebra-cli and zebra-client crates (#6726) 2023-05-19 04:45:54 +00:00
LICENSE-APACHE Update copyright year in Apache License (#6140) 2023-02-12 22:46:21 +00:00
LICENSE-MIT Update copyright year in MIT License (#6131) 2023-02-12 22:46:11 +00:00
README.md change(docs): Update User Docs (#6733) 2023-05-23 13:18:57 +00:00
SECURITY.md Explicitly allow unencrypted disclosures for alpha releases (#2127) 2021-05-11 14:41:33 +02:00
clippy.toml Apply clippy fixes 2020-02-05 12:42:32 -08:00
codecov.yml Re-enable code coverage comments on PRs (#3246) 2021-12-22 00:52:08 +00:00
deny.toml fix(ci): Give more time to the inbound service when queueing requests (#6691) 2023-05-16 23:55:17 +00:00
firebase.json Configure redirect for firebase hosting 2020-01-16 18:38:16 -05:00
katex-header.html Add KaTeX to rendered docs. (#832) 2020-08-05 17:34:30 -07:00
prometheus.yaml Tell Prometheus to scrape more aggressively 2020-02-14 20:14:05 -05:00

README.md

Zebra logotype


CI Docker CI OSes Continuous Delivery codecov Build docs License

Contents

About

Zebra is the Zcash Foundation's independent, consensus-compatible implementation of a Zcash node, currently under development. It can be used to join the Zcash peer-to-peer network, which helps keeping Zcash working by validating and broadcasting transactions, and maintaining the Zcash blockchain state in a distributed manner.

Zcash is a cryptocurrency designed to preserve the user's privacy. If you just want to send and receive Zcash then you don't need to use Zebra directly. You can download a Zcash wallet application which will handle that for you.

Please join us on Discord if you'd like to find out more or get involved!

Using Zebra

You would want to run Zebra if you want to contribute to the Zcash network: the more nodes are run, the more reliable the network will be in terms of speed and resistance to denial of service attacks, for example.

Zebra validates blocks and transactions, but needs extra software to generate them:

Zebra's network stack is interoperable with zcashd, and Zebra implements all the features required to reach Zcash network consensus, including the validation of all the consensus rules for the NU5 network upgrade. Here are some benefits of Zebra.

Getting Started

You can run Zebra using our Docker image or you can build it manually. Please see the System Requirements section in the Zebra book for system requirements.

Docker

This command will run our latest release, and sync it to the tip:

docker run zfnd/zebra:1.0.0-rc.8

For more information, read our Docker documentation.

Building Zebra

Building Zebra requires Rust, libclang, pkg-config, and a C++ compiler.

Zebra is tested with the latest stable Rust version. Earlier versions are not supported or tested. Note that Zebra's code currently uses features introduced in Rust 1.68, or any later stable release.

Every few weeks, we release a new Zebra version.

Below are quick summaries for installing the dependencies on your machine.

General instructions for installing dependencies

  1. Install cargo and rustc.

  2. Install Zebra's build dependencies:

    • libclang is a library that might have different names depending on your package manager. Typical names are libclang, libclang-dev, llvm, or llvm-dev.
    • clang or another C++ compiler: g++ (all platforms) or Xcode (macOS).
    • pkg-config

Dependencies on Arch

sudo pacman -S rust clang pkgconf

Note that the package clang includes libclang as well as the C++ compiler.

Once the dependencies are in place, you can build Zebra

cargo install --locked --git https://github.com/ZcashFoundation/zebra --tag v1.0.0-rc.8 zebrad

You can start Zebra by

zebrad start

See the Running Zebra section in the book for more details.

Optional Features

You can also build Zebra with additional Cargo features:

You can combine multiple features by listing them as parameters of the --features flag:

cargo install --features="<feature1> <feature2> ..." ...

Our full list of experimental and developer features is in the API documentation.

Some debugging and monitoring features are disabled in release builds to increase performance.

Network Ports

Zebra uses the following inbound and outbound TCP ports:

  • 8233 on Mainnet
  • 18233 on Testnet

Please see the Network Requirements section of the Zebra book for more details.

Known Issues

There are a few bugs in Zebra that we're still working on fixing:

  • If Zebra fails downloading the Zcash parameters, use the Zcash parameters download script instead.

  • Block download and verification sometimes times out during Zebra's initial sync #5709. The full sync still finishes reasonably quickly.

  • No Windows support #3801. We used to test with Windows Server 2019, but not any more; see the issue for details.

  • Experimental Tor support is disabled until Zebra upgrades to the latest arti-client. This happened due to a Rust dependency conflict, which could only be resolved by arti upgrading to a version of x25519-dalek with the dependency fix.

  • Output of help, --help flag, and usage of invalid commands or options are inconsistent #5502. See the issue for details.

Future Work

The Zebra team is currently working towards an audited stable release.

We will continue to add new features as part of future network upgrades, and in response to community feedback.

Documentation

The Zebra website contains user documentation, such as how to run or configure Zebra, set up metrics integrations, etc., as well as developer documentation, such as design documents. We also render API documentation for the external API of our crates, as well as internal documentation for private APIs.

Security

Zebra has a responsible disclosure policy, which we encourage security researchers to follow.

License

Zebra is distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT.