e957192c54
When no `-rpcpassword` is specified, use a special 'cookie' file for authentication. This file is generated with random content when the daemon starts, and deleted when it exits. Read access to this file controls who can access through RPC. By default this file is stored in the data directory but it be overriden with `-rpccookiefile`. This is similar to Tor CookieAuthentication: see https://www.torproject.org/docs/tor-manual.html.en Alternative to #6258. Like that pull, this allows running bitcoind without any manual configuration. However, daemons should ideally never write to their configuration files, so I prefer this solution.
Zcash 1.0.4
What is Zcash?
Zcash is an implementation of the "Zerocash" protocol. Based on Bitcoin's code, it intends to offer a far higher standard of privacy through a sophisticated zero-knowledge proving scheme that preserves confidentiality of transaction metadata. Technical details are available in our Protocol Specification.
This software is the Zcash client. It downloads and stores the entire history of Zcash transactions; depending on the speed of your computer and network connection, the synchronization process could take a day or more once the blockchain has reached a significant size.
Security Warnings
See important security warnings in doc/security-warnings.md.
Zcash is unfinished and highly experimental. Use at your own risk.
Where do I begin?
We have a guide for joining the main Zcash network: https://github.com/zcash/zcash/wiki/1.0-User-Guide
Need Help?
- See the documentation at the Zcash Wiki for help and more information.
- Ask for help on the Zcash forum.
Participation in the Zcash project is subject to a Code of Conduct.
Building
Build Zcash along with most dependencies from source by running ./zcutil/build.sh. Currently only Linux is officially supported.
License
For license information see the file COPYING.