ZCash
z.cashUses zero-knowledge proofs to protect privacy cryptographic technique, that allows two users to transact without ever revealing their true identity or address. The Zcash blockchain uses two types of addresses and transactions, Z transactions and addresses are private and T transactions and addresses are transparent like Bitcoin.
- Homepage: z.cash
- GitHub: github.com/zcash/zcash
- Privacy: tosdr.org/en/service/8258
- Web info: web-check.xyz/results/z.cash
ZCash Source Code
Author
Description
Zcash - Internet Money
Homepage
https://z.cash/License
NOASSERTION
Created
22 Nov 14
Last Updated
29 Nov 24
Latest version
Primary Language
C++
Size
113,584 KB
Stars
4,948
Forks
2,051
Watchers
4,948
Language Usage
Star History
Top Contributors
-
@laanwj (2899)
-
@str4d (2541)
-
@nuttycom (1115)
-
@gavinandresen (1100)
-
@sipa (1082)
-
@zkbot (1053)
-
@daira (593)
-
@ebfull (511)
-
@bitcartel (487)
-
@theuni (368)
-
@non-github-bitcoin (271)
-
@sellout (231)
-
@luke-jr (212)
-
@jonasschnelli (200)
-
@gmaxwell (185)
-
@TheBlueMatt (157)
-
@defuse (142)
-
@fanquake (134)
-
@oxarbitrage (122)
-
@softminus (103)
-
@therealyingtong (97)
-
@LarryRuane (89)
-
@jtimon (81)
-
@petertodd (73)
-
@cozz (70)
-
@charlieok (51)
-
@sdaftuar (50)
-
@morcos (49)
-
@paveljanik (46)
-
@pstratem (46)
Recent Commits
-
Merge pull request #6964 from daira/mining-test-comment-offbyone Miner tests: correct a comment, and add another similar comment where it applies
-
Merge pull request #6965 from daira/fix-getblocksubsidy-suggestions Fix getblocksubsidy suggestions
-
Merge pull request #6967 from daira/fix-test_checkblock gtest/test_checkblock.cpp: fix a bug in MockCValidationState that was causing a test warning
-
Merge pull request #6968 from daira/update-daira-emma-keys Update Daira-Emma's gpg keys
-
Update Daira-Emma Hopwood's gpg keys. The key referred to by `daira-emma-old.asc` was used to sign the tags for zcashd v1.0.0-rc1, v1.0.0-rc2, and v1.0.0-rc3. All other zcashd signatures made by Daira-Emma used the key referred to by `daira-emma.asc`. Signed-off-by: Daira-Emma Hopwood <[email protected]>
-
Miner tests: correct a comment, and add another similar comment where it applies. Doc-only. Signed-off-by: Daira-Emma Hopwood <[email protected]>
-
gtest/test_checkblock.cpp: fix a bug in MockCValidationState that was causing a test warning. Signed-off-by: Daira-Emma Hopwood <[email protected]>
-
Simplify `GetActiveFundingStreamElements`. Signed-off-by: Daira-Emma Hopwood <[email protected]>
-
sapling::Builder: add funding stream outputs in a more predictable order. Previously it was deterministic, but depended on details of the `operator<` implementations of `FundingStreamRecipient`, `SaplingPaymentAddress`, and `CScript`. Now it is just the same order as in `vFundingStreams`. Signed-off-by: Daira-Emma Hopwood <[email protected]>
-
Funding streams: Rename INSUFFICIENT_ADDRESSES to INSUFFICIENT_RECIPIENTS. Signed-off-by: Daira-Emma Hopwood <[email protected]>
-
Merge pull request #6966 from zcash/version-6.0.0 Version 6.0.0 post-release merge.
-
Merge pull request #6958 from zcash/release-v6.0.0 Release v6.0.0
-
Merge pull request #6962 from daira/fix-miner-future-timestamp Ensure that the "future timestamp" rule is correctly applied by block template construction
-
Merge pull request #6963 from str4d/fix-getblocksubsidy Fix `getblocksubsidy`
-
Fix specification URL for NU6 lockbox
-
test: Update `getblocksubsidy` test with NU6 mainnet funding streams
-
rpc: Fetch correct funding streams in `getblocksubsidy` The previous logic was indexing into the global funding streams list with the local index into the active funding streams. This worked fine for the first funding stream period, but once a funding stream ended and another was enabled, the indices no longer matched. We now return the `FundingStream` from `GetActiveFundingStreams`, as the only user of that method is `getblocksubsidy`.
-
Ensure that the "future timestamp" rule is correctly applied by block template construction. fixes #6960 Signed-off-by: Daira-Emma Hopwood <[email protected]>
-
Changes necessary for NU6 funding streams and activation height. Co-authored-by: Jack Grigg <[email protected]> Signed-off-by: Daira-Emma Hopwood <[email protected]>
-
debian: Set urgency of 6.0.0 release to `high`
-
make-release.py: Updated book for 6.0.0.
-
make-release.py: Updated release notes and changelog for 6.0.0.
-
make-release.py: Updated manpages for 6.0.0.
-
make-release.py: Versioning changes for 6.0.0.
-
Update release notes for 6.0.0
-
Set support window back to the usual 16 weeks
-
Migrate to librustzcash crates revision right before NU6 mainnet height This gets the other side-effects of the recent changes out of the way, and then in the commit where we set the mainnet activation height in `zcashd`, we can do so uniformly across the stack.
-
qa: Add latest Clang release to postponed updates
-
Merge pull request #6957 from daira/code-of-conduct-update Update contacts in the Code of Conduct
-
Code of Conduct: add Kris and Str4d as contacts. Signed-off-by: Daira-Emma Hopwood <[email protected]>
ZCash Website
Website
Zcash: Privacy-protecting digital currency
A simple, secure digital currency that protects your privacy. For everyday purchases, sending money to a friend, and your favorite crypto applications, too.
Redirects
Does not redirect
Security Checks
2 security checks failed (64 passed)
- Top-Level Domain Highly Abused
- Domain is Blacklisted
Server Details
- IP Address 104.16.174.83
- Location San Francisco, California, United States of America, NA
- ISP CloudFlare Inc.
- ASN AS13335
Associated Countries
-
US
Saftey Score
Website marked as very dangerous
0%
Blacklist Check
z.cash was found on 1 blacklists
- CoinBlockerLists
- ThreatLog
- OpenPhish
- PhishTank
- Phishing.Database
- PhishStats
- URLhaus
- RPiList Not Serious
- AntiSocial Blacklist
- PhishFeed
- NABP Not Recommended Sites
- Spam404
- CRDF
- Artists Against 419
- CERT Polska
- PetScams
- Suspicious Hosting IP
- Phishunt
- MetaMask EthPhishing
- EtherScamDB
- EtherAddressLookup
- ViriBack C2 Tracker
- Bambenek Consulting
- Badbitcoin
- SecureReload Phishing List
- Fake Website Buster
- TweetFeed
- CryptoScamDB
- StopGunScams
- ThreatFox
- PhishFort
Website Preview
ZCash Reviews
More Cryptocurrencies
-
One of the most private cryptocurrencies, since no meta data is available (not even the transaction amount). It uses complex on-chain cryptographic methods such as Ring signatures, RingCT, Kovri, and Stealth addresses all of which help protect the privacy of users.
About the Data: ZCash
API
You can access ZCash's data programmatically via our API.
Simply make a GET request to:
https://api.awesome-privacy.xyz/finance/cryptocurrencies/zcashThe REST API is free, no-auth and CORS-enabled. To learn more, view the Swagger Docs or read the API Usage Guide.
About the Data
Beyond the user-submitted YAML you see above, we also augment each listing with additional data dynamically fetched from several sources. To learn more about where the rest of data included in this page comes from, and how it is computed, see the About the Data section of our About page.
Share ZCash
Help your friends compare Cryptocurrencies, and pick privacy-respecting software and services.
Share ZCash and Awesome Privacy with your network!