kazcw 56f165bdc1 prevent peer flooding request queue for an inv
mapAlreadyAskedFor does not keep track of which peer has a request queued for a
particular tx. As a result, a peer can blind a node to a tx indefinitely by
sending many invs for the same tx, and then never replying to getdatas for it.
Each inv received will be placed 2 minutes farther back in mapAlreadyAskedFor,
so a short message containing 10 invs would render that tx unavailable for 20
minutes.

This is fixed by disallowing a peer from having more than one entry for a
particular inv in mapAlreadyAskedFor at a time.
2016-09-15 23:17:34 -07:00
2015-07-27 13:09:25 +02:00
2016-09-05 12:00:50 -06:00
2016-09-09 00:41:41 -06:00
2015-06-25 17:10:09 +02:00
2016-01-20 00:38:40 -07:00
2016-02-18 17:16:28 -07:00

Zcash

https://z.cash/

Where do I begin?

We have a guide for joining the public testnet: https://github.com/zcash/zcash/wiki/Public-Alpha-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.

Description
No description provided
Readme 174 MiB
Languages
C++ 44.3%
Shell 28.4%
C 19.4%
Python 4.5%
M4 1%
Other 2.3%