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

bitcoin blockchain c-plus-plus cryptocurrency decentralized lbry

Find a file

Pieter Wuille 7c4c207be8 Merge pull request #3211 `b64187d` Rename leveldb.{h,cpp} to leveldbwrapper.{h,cpp}. (Brandon Dahler)		2013-11-09 18:46:32 +01:00
contrib	Check integrity of gitian input source tarballs	2013-10-31 17:56:55 -10:00
doc	Merge pull request #3123 from super3/master	2013-10-22 08:10:17 -07:00
qa/pull-tester	Skip comparison tool on win32 since Wine breaks it	2013-11-04 00:40:39 -05:00
share	fix extract_strings_qt.py	2013-09-19 14:59:45 +02:00
src	Rename leveldb.{h,cpp} to leveldbwrapper.{h,cpp}.	2013-11-08 18:03:46 -06:00
.gitattributes	Build identification strings	2012-04-10 18:16:53 +02:00
.gitignore	.gitignore: Simplify references to the same file in different directories	2013-11-02 08:29:31 -07:00
autogen.sh	autotools: switch to autotools buildsystem	2013-09-05 21:31:03 -04:00
configure.ac	Make large-reorg tests optional in block-tester	2013-10-28 01:16:41 -04:00
COPYING	Bump version numbers for 0.8 release	2013-01-30 14:19:09 -05:00
INSTALL	Prettify some /Contrib READMEs	2013-10-21 20:07:31 -04:00
Makefile.am	Fix port binding by listening on port $BASHPID	2013-10-28 03:43:09 -04:00
pkg.m4	autotools: switch to autotools buildsystem	2013-09-05 21:31:03 -04:00
README.md	Documentation Cleanup in /Doc	2013-10-12 18:39:26 -04:00

README.md

Bitcoin integration/staging tree

http://www.bitcoin.org

What is Bitcoin?

Bitcoin is an experimental new 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 is also the name of the open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Bitcoin client software, see http://www.bitcoin.org.

License

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

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.

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 the code doesn't match the project's coding conventions (see doc/coding.md) or are controversial.

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.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test. Please be patient and help out, 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

Every pull request is built for both Windows and Linux on a dedicated server, and unit and sanity tests are automatically run. The binaries produced may be used for manual QA testing — a link to them will appear in a comment on the pull request posted by BitcoinPullTester. See https://github.com/TheBlueMatt/test-scripts for the build/test scripts.

Manual Quality Assurance (QA) Testing

Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code. See https://github.com/bitcoin/QA/ for how to create a test plan.