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

bitcoin blockchain c-plus-plus cryptocurrency decentralized lbry

Find a file

Matt Corallo cbfc77352d Short-circuit bloom checking if we will always return true. This allows full nodes to use bloom filters as an optimization.		2013-02-24 20:36:59 -05:00
contrib	reformat OS X build instrcs, add 10.8 + Homebrew	2013-02-19 21:45:39 -05:00
doc	reformat OS X build instrcs, add 10.8 + Homebrew	2013-02-19 21:45:39 -05:00
share	Reimplement click-to-pay links. Add OSX support.	2013-02-12 15:41:31 -05:00
src	Short-circuit bloom checking if we will always return true.	2013-02-24 20:36:59 -05:00
.gitattributes	Build identification strings	2012-04-10 18:16:53 +02:00
.gitignore	Import LevelDB 1.5, it will be used for the transaction database.	2012-10-20 23:08:56 +02:00
bitcoin-qt.pro	Merge pull request #2186 from Diapolo/misc_stuff	2013-02-23 23:52:27 -08:00
COPYING	Bump version numbers for 0.8 release	2013-01-30 14:19:09 -05:00
INSTALL	Update master	2012-06-21 09:36:20 +08:00
README.md	Fix qt unit test build on OSX	2013-02-22 11:41:23 -05: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 sofware, 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.txt) 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 for the core code are in src/test/. To compile and run them:

cd src; make -f makefile.linux test

Unit tests for the GUI code are in src/qt/test/. To compile and run them:

qmake BITCOIN_QT_TEST=1 -o Makefile.test bitcoin-qt.pro
make -f Makefile.test
./bitcoin-qt_test

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.