d8f5d6b6f1
* Add support for deleting the trees * Prune the trees * Remove `Network` from `DiskWriteBatch` Removing the `Network` from `DiskWriteBatch` makes it easy to instantiate `DiskWriteBatch`es in `ZebraDb` that remove individual note commitment trees. The `Network` from `DiskWriteBatch` was used only for transparent addresses, so the refactor isn't large. After removing it from `DiskWriteBatch`, I passed it as a function argument instead. However, we should simplify the parameter lists because at least two functions have more than seven parameters now. * Support individual tree removal in `ZebraDb` * Refactor the tree removal task * Prune old comments * Remove redundant code * Batch the removals * delete ranges before relevant network upgrades * moves prev_tree inits * add iterator methods for reading note commitment trees * Sets up skeleton of sapling pipeline * Replaces .filter with .take_while Fills in pipeline Reuses zs_range_iter instead of repeating that code Updates logic to stop at initial tip height * uses std threads * delete_range excludes end key * fixes off by one bugs * Log warning when a send fails * Removes progress logs * Log join errors instead of panicking * Revert: Make the `db` field of `ZebraDb` private * Move `delete_range_sapling_tree` * Remove a redundant `else if` branch Rationale: The condition `n == 1` for the removed branch is true for a subset of values of `n` in the preceding condition `n >= 1`. * Use more specific error messages * Revert: Remove redundant methods for tree removal * Suggestions for Deduplicate note commitment trees stored in the finalized state (#7330) * Add TODOs to some `Height` methods * Add methods for deleting individual trees * Refactor the tasks for deleting trees --------- Co-authored-by: arya2 <aryasolhi@gmail.com> |
||
|---|---|---|
| .cargo | ||
| .github | ||
| book | ||
| docker | ||
| grafana | ||
| tower-batch-control | ||
| tower-fallback | ||
| zebra-chain | ||
| zebra-consensus | ||
| zebra-network | ||
| zebra-node-services | ||
| zebra-rpc | ||
| zebra-script | ||
| zebra-state | ||
| zebra-test | ||
| zebra-utils | ||
| zebrad | ||
| .codespellrc | ||
| .dockerignore | ||
| .firebaserc | ||
| .gitattributes | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| README.md | ||
| SECURITY.md | ||
| clippy.toml | ||
| codecov.yml | ||
| deny.toml | ||
| firebase.json | ||
| katex-header.html | ||
| prometheus.yaml | ||
| release.toml | ||
README.md
Contents
About
Zebra is the Zcash Foundation's independent, consensus-compatible implementation of a Zcash node.
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.
Zebra validates blocks and transactions, but needs extra software to generate them:
- To generate transactions, run Zebra with
lightwalletd. - To generate blocks, enable mining support, and use a mining pool or miner with Zebra's mining JSON-RPCs. Mining support is currently incomplete, experimental, and off by default.
Please join us on Discord if you'd like to find out more or get involved!
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:latest
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. Any Zebra release can start depending on new features in the
latest stable Rust.
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
-
Install
cargoandrustc. -
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, orllvm-dev. - clang or another C++ compiler:
g++(all platforms) orXcode(macOS). - pkg-config
- libclang is a library that might have different names depending on your
package manager. Typical names are
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 and install Zebra:
cargo install --locked zebrad
You can start Zebra by
zebrad start
See the Installing Zebra and Running Zebra sections in the book for more details.
Optional Features
You can also build Zebra with additional Cargo features:
sentryfor Sentry monitoringjournaldforjournaldloggingprometheusfor Prometheus metricsgetblocktemplate-rpcsfor mining support
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:
-
Zebra currently gossips and connects to private IP addresses, we want to disable private IPs but provide a config (#3117) in an upcoming release
-
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.
-
Rust 1.70 causes crashes during shutdown on macOS x86_64 (#6812). The state cache should stay valid despite the crash.
-
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 byartiupgrading to a version ofx25519-dalekwith the dependency fix.
Future Work
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.
User support
For bug reports please open a bug report ticket in the Zebra repository.
Alternatively by chat, Join the Zcash Foundation Discord Server and find the #zebra-support channel.
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.
Some Zebra crates are distributed under the MIT license only, because some of their code was originally from MIT-licensed projects. See each crate's directory for details.