maxmustermann/dogecoin
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
9994 commits 12 branches 161 tags 1.2 GiB
C++ 65.7%
Python 15%
C 12.5%
M4 2.7%
Makefile 1.5%
Other 2.5%
Go to file
Cory Fields f3d3eaf78e release: add check-symbols and check-security make targets 
These are not added to the default checks because some of them depend on
release-build configs.
2016-01-26 23:07:04 -05:00
.tx qt: translation update prior to opening 0.12 translations 2015-11-01 16:11:50 +01:00
build-aux/m4 build: Use fPIC rather than fPIE for qt objects. 2015-11-09 22:50:31 -05:00
contrib release: add _IO_stdin_used to ignored exports 2016-01-26 23:07:04 -05:00
depends c++11: fix libbdb build against libc++ in c++11 mode 2016-01-05 17:17:29 -05:00
doc gitian: Need ca-certificates and python for LXC builds 2016-01-18 10:59:14 +01:00
qa Merge #7236: Use createrawtx locktime parm in txn_clone 2016-01-22 16:57:47 +01:00
share Update project URL 2016-01-15 07:45:39 +00:00
src release: add check-symbols and check-security make targets 2016-01-26 23:07:04 -05:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore Merge pull request #6813 2015-10-26 09:09:33 +01:00
.travis.yml [travis] Run contrib/devtools/check-doc.py early 2016-01-18 14:00:02 +01:00
autogen.sh Bugfix: Replace bashisms with standard sh to fix build on non-BASH systems 2014-10-03 23:45:26 +00:00
configure.ac release: add check-symbols and check-security make targets 2016-01-26 23:07:04 -05:00
CONTRIBUTING.md Note that reviewers should mention the commit hash of the commits they reviewed. 2015-12-10 22:44:09 -08:00
COPYING Update license year range to 2016 2016-01-17 23:38:11 +05:30
INSTALL Prettify some /Contrib READMEs 2013-10-21 20:07:31 -04:00
libbitcoinconsensus.pc.in libbitcoinconsensus: Add pkg-config support 2014-11-20 21:23:34 +00:00
Makefile.am release: add check-symbols and check-security make targets 2016-01-26 23:07:04 -05:00
README.md Update project URL 2016-01-15 07:45:39 +00:00

README.md

Bitcoin Core integration/staging tree

Build Status

https://bitcoincore.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 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://www.bitcoin.org/en/download.

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.

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #bitcoin-core-dev.

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

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run with: qa/pull-tester/rpc-tests.py

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

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.