slackcoder/bitcoin - Bitcoin Code integration/staging tree

Age	Commit message (Collapse)	Author
2017-03-21	[trivial] Fix typos in comments	practicalswift

2016-12-31	Increment MIT Licence copyright header year on files modified in 2016	isle2983
	Edited via: $ contrib/devtools/copyright_header.py update .
2016-11-19	Introduce convenience type CTransactionRef	Pieter Wuille

2016-11-19	Make CBlock::vtx a vector of shared_ptr<CTransaction>	Pieter Wuille

2016-11-07	test: Fix test_random includes	MarcoFalke

2016-10-17	Kill insecure_random and associated global state	Wladimir J. van der Laan
	There are only a few uses of `insecure_random` outside the tests. This PR replaces uses of insecure_random (and its accompanying global state) in the core code with an FastRandomContext that is automatically seeded on creation. This is meant to be used for inner loops. The FastRandomContext can be in the outer scope, or the class itself, then rand32() is used inside the loop. Useful e.g. for pushing addresses in CNode or the fee rounding, or randomization for coin selection. As a context is created per purpose, thus it gets rid of cross-thread unprotected shared usage of a single set of globals, this should also get rid of the potential race conditions. - I'd say TxMempool::check is not called enough to warrant using a special fast random context, this is switched to GetRand() (open for discussion...) - The use of `insecure_rand` in ConnectThroughProxy has been replaced by an atomic integer counter. The only goal here is to have a different credentials pair for each connection to go on a different Tor circuit, it does not need to be random nor unpredictable. - To avoid having a FastRandomContext on every CNode, the context is passed into PushAddress as appropriate. There remains an insecure_random for test usage in `test_random.h`.
2016-01-17	Typo fixes in comments	Chris Wheeler

2015-11-27	Switch blocks to a constant-space Merkle root/branch algorithm.	Pieter Wuille
	This switches the Merkle tree logic for blocks to one that runs in constant (small) space. The old code is moved to tests, and a new test is added that for various combinations of block sizes, transaction positions to compute a branch for, and mutations: * Verifies that the old code and new code agree for the Merkle root. * Verifies that the old code and new code agree for the Merkle branch. * Verifies that the computed Merkle branch is valid. * Verifies that mutations don't change the Merkle root. * Verifies that mutations are correctly detected.