zecfoundation
/
zcashd
mirror of https://github.com/ZcashFoundation/zcashd.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
1,538 Commits 27 Branches 108 Tags 109 MiB
C++ 61.5%
Python 19.6%
C 10.2%
Rust 3.8%
Shell 1.7%
Other 3.2%
Go to file
Michael Hendricks 1c4aab926e Retain only the most recent time samples 
Remembering all time samples makes nTimeOffset slow to respond to
system clock corrections.  For instance, I start my node with a system
clock that's 30 minutes slow and run it for a few days.  During that
time, I accumulate 10,000 offset samples with a median of 1800
seconds.  Now I correct my system clock.  Without this change, my node
must collect another 10,000 samples before nTimeOffset is correct
again.  With this change, I must only accumulate 100 samples to
correct the offset.

Storing unlimited time samples also allows an attacker with many IP
addresses (ex, a large botnet) to perform a memory exhaustion attack
against Bitcoin nodes.  The attacker sends a version message from each
IP to his target, consuming more of the target's memory each time.
Time samples are small, so this attack might be impractical under the
old code, but it's impossible with the new code.
 		2011-12-01 17:28:14 -07:00
contrib Update contrib/debian/ for 0.5.0 release and fix copyright file. 2011-11-21 11:55:45 -05:00
doc Don't forget to bump release numbers in READMEs next time 2011-11-21 14:38:47 -05:00
scripts/qt move qt-specific scripts to qt-specific directory in scripts/ 2011-09-18 12:44:32 +02:00
share Bump version to 0.5.1 2011-11-21 13:38:38 -05:00
src Retain only the most recent time samples 2011-12-01 17:28:14 -07:00
.gitignore Output build temp files in build/ instead of current directory. 2011-09-26 13:14:34 -04:00
COPYING directory re-organization (keeps the old build system) 2011-04-23 12:10:25 +02:00
INSTALL Update build instructions for the new, no-wxwidgets world 2011-09-26 11:40:43 -04:00
README directory re-organization (keeps the old build system) 2011-04-23 12:10:25 +02:00
README.md Updated readme file with timers. 2011-09-26 22:22:19 -04:00
bitcoin-qt.pro Moved checkpoints out of main, to prep for using them to help prevent DoS attacks 2011-12-01 12:18:50 -05:00

README.md

Bitcoin integration/staging tree

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the bitcoin development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list: http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don't match the project's coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new official, stable release versions of Bitcoin. If you would like to help test the Bitcoin core, please contact QA@BitcoinTesting.org.

Feature branches are created when there are major new features being worked on by several people.

From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'.

Requests to reopen closed pull requests and/or issues can be submitted to QA@BitcoinTesting.org.