0df0ce05f0
Verify TLS certificates w/ wget in fetch-params.sh Per NCC-2016-017, wget was being run with `--no-check-certificate`, which means that the connection can be man-in-the-middled, even if we are verifying the integrity of the parameters later via hash sums. The rationale cited in the Bash comments does not stand up to scrutiny. There's really no persuasive reason not to verify certificates. Fixes #1346. |
||
---|---|---|
.tx | ||
build-aux/m4 | ||
contrib | ||
depends | ||
doc | ||
qa | ||
share | ||
src | ||
zcutil | ||
.gitattributes | ||
.gitignore | ||
.travis.yml | ||
COPYING | ||
INSTALL | ||
Makefile.am | ||
README.md | ||
autogen.sh | ||
code_of_conduct.md | ||
configure.ac | ||
libbitcoinconsensus.pc.in |
README.md
Zcash
Where do I begin?
We have a guide for joining the public testnet: https://github.com/zcash/zcash/wiki/Beta-Guide
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 and anonymity through a sophisticiated zero-knowledge proving scheme which preserves confidentiality of transaction metadata.
Zcash is unfinished and highly experimental. Use at your own risk.
Participation in the Zcash project is subject to a Code of Conduct.
Security Warnings
See important security warnings in doc/security-warnings.md.
License
Zcash is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.