The blockchain that provides the digital content namespace for the LBRY protocol

bitcoin blockchain c-plus-plus cryptocurrency decentralized lbry

Find a file

Wladimir J. van der Laan 6e6b3b944d Merge #14955 : Switch all RNG code to the built-in PRNG `223de8d94d` Document RNG design in random.h (Pieter Wuille) `f2e60ca985` Use secure allocator for RNG state (Pieter Wuille) `cddb31bb0a` Encapsulate RNGState better (Pieter Wuille) `152146e782` DRY: Implement GetRand using FastRandomContext::randrange (Pieter Wuille) `a1f252eda8` Sprinkle some sweet noexcepts over the RNG code (Pieter Wuille) `4ea8e50837` Remove hwrand_initialized. (Pieter Wuille) `9d7032e4f0` Switch all RNG code to the built-in PRNG. (Pieter Wuille) `16e40a8b56` Integrate util/system's CInit into RNGState (Pieter Wuille) `2ccc3d3aa3` Abstract out seeding/extracting entropy into RNGState::MixExtract (Pieter Wuille) `aae8b9bf0f` Add thread safety annotations to RNG state (Pieter Wuille) `d3f54d1c82` Rename some hardware RNG related functions (Pieter Wuille) `05fde14e3a` Automatically initialize RNG on first use. (Pieter Wuille) `2d1cc50939` Don't log RandAddSeedPerfmon details (Pieter Wuille) `6a57ca91da` Use FRC::randbytes instead of reading >32 bytes from RNG (Pieter Wuille) Pull request description: This does not remove OpenSSL, but makes our own PRNG the 'main' one; for GetStrongRandBytes, the OpenSSL RNG is still used (indirectly, by feeding its output into our PRNG state). It includes a few policy changes (regarding what entropy is seeded when). Before this PR: * GetRand: OpenSSL * GetStrongRand: CPU cycle counter * Perfmon data (on Windows, once 10 min) * /dev/urandom (or equivalent) * rdrand (if available) * From scheduler when idle: * CPU cycle counter before and after 1ms sleep * At startup: * CPU cycle counter before and after 1ms sleep After this PR: * GetRand: Stack pointer (which indirectly identifies thread and some call stack information) * rdrand (if available) * CPU cycle counter * GetStrongRand: Stack pointer (which indirectly identifies thread and some call stack information) * rdrand (if available) * CPU cycle counter * /dev/urandom (or equivalent) * OpenSSL * CPU cycle counter again * From scheduler when idle: * Stack pointer (which indirectly identifies thread and some call stack information) * rdrand (if available) * CPU cycle counter before and after 1ms sleep * Perfmon data (on Windows, once every 10 min) * At startup: * Stack pointer (which indirectly identifies thread and some call stack information) * rdrand (if available) * CPU cycle counter * /dev/urandom (or equivalent) * OpenSSL * CPU cycle counter again * Perfmon data (on Windows, once every 10 min) The interface of random.h is also simplified, and documentation is added. This implements most of #14623. Tree-SHA512: 0120e19bd4ce80a509b5c180a4f29497d299ce8242e25755880851344b825bc2d64a222bc245e659562fb5463fb7c70fbfcf003616be4dc59d0ed6534f93dd20		2019-01-21 19:46:45 +01:00
.github	Get more info about GUI-related issue on Linux	2018-12-27 06:53:07 +02:00
.travis	Pin shellcheck version to v0.6.0	2019-01-16 15:47:56 +01:00
.tx	tx: Update transifex slug 016x→017x	2018-08-02 13:42:15 +02:00
build-aux/m4	Bump the minimum Qt version to 5.2	2018-11-14 01:32:51 +02:00
build_msvc	Merge #14151 : windows: Fix remaining compiler warnings (MSVC)	2019-01-16 13:50:37 +01:00
contrib	build: Drop macports support	2019-01-16 12:13:59 -08:00
depends	Update zmq to 4.3.1	2019-01-18 10:25:14 +02:00
doc	Merge #15177 : rest: Improve tests and documention of /headers and /block	2019-01-21 17:37:55 +01:00
share	Merge #14701 : build: Add CLIENT_VERSION_BUILD to CFBundleGetInfoString	2018-12-12 16:24:52 +01:00
src	Merge #14955 : Switch all RNG code to the built-in PRNG	2019-01-21 19:46:45 +01:00
test	Merge #15177 : rest: Improve tests and documention of /headers and /block	2019-01-21 17:37:55 +01:00
.appveyor.yml	Fix remaining compiler warnings (MSVC). Move disabling of specific warnings from /nowarn to project file.	2019-01-15 20:15:26 +01:00
.gitattributes	Separate protocol versioning from clientversion	2014-10-29 00:24:40 -04:00
.gitignore	gitignore contents of db4 folder	2018-10-19 12:15:47 +08:00
.python-version	[test] Travis: enforce Python 3.4 support in functional tests	2018-12-12 10:39:32 +01:00
.travis.yml	Merge #15020 : Build: add names to Travis jobs	2019-01-03 16:42:34 +01:00
autogen.sh	Add "export LC_ALL=C" to all shell scripts	2018-06-14 15:27:52 +02:00
configure.ac	build: Drop macports support	2019-01-16 12:13:59 -08:00
CONTRIBUTING.md	Botbot.me (IRC logs) not available anymore	2019-01-01 16:04:38 +02:00
COPYING	[Trivial] Update license year range to 2019	2018-12-31 04:27:59 +01:00
INSTALL.md	Update INSTALL landing redirection notice for build instructions.	2016-10-06 12:27:23 +13:00
libbitcoinconsensus.pc.in	Unify package name to as few places as possible without major changes	2015-12-14 02:11:10 +00:00
Makefile.am	build: Add bitcoin-tx.exe into Windows installer	2018-11-09 21:57:13 +08:00
README.md	[doc] conf: Remove deprecated options from docs, Other cleanup	2018-11-07 13:30:03 -05:00

README.md

Bitcoin Core integration/staging tree

https://bitcoincore.org

What is Bitcoin?

Bitcoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin Core is the name of open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Bitcoin Core software, see https://bitcoincore.org/en/download/, or read the original whitepaper.

License

Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Bitcoin Core.

The contribution workflow is described in CONTRIBUTING.md and useful hints for developers can be found in doc/developer-notes.md.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

Translations

Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also subscribe to the mailing list.