Ви не можете вибрати більше 25 тем Теми мають розпочинатися з літери або цифри, можуть містити дефіси (-) і не повинні перевищувати 35 символів.
Michael Ford 1e3473d384 Add operator names to DNS Seed list 6 роки тому
.tx qt: Change transifex slug to new resource for 0.10.x 6 роки тому
build-aux/m4 Suggest --disable-wallet when libdb_cxx headers are missing 6 роки тому
contrib Remove leftover strlcpy.h copyright 5 роки тому
depends depends: latest config.guess and config.sub 5 роки тому
doc Re-wrote a passage of text that was difficult to understand. 5 роки тому
qa Fix CheckBlockIndex for reindex. 5 роки тому
share Update seed IPs, based on bitcoin.sipa.be crawler data 6 роки тому
src Add operator names to DNS Seed list 5 роки тому
.gitattributes Separate protocol versioning from clientversion 6 роки тому
.gitignore Add libbitcoinconsensus.pc to .gitignore 6 роки тому
.travis.yml Reorder travis builds for faster response 6 роки тому
COPYING Updated license date 6 роки тому
INSTALL Prettify some /Contrib READMEs 7 роки тому
Makefile.am osx packaging: switch background image to background.tiff 6 роки тому
README.md Remove redundant copyright notices from README files 6 роки тому
autogen.sh Bugfix: Replace bashisms with standard sh to fix build on non-BASH systems 6 роки тому
configure.ac build: Endian compatibility 6 роки тому
libbitcoinconsensus.pc.in libbitcoinconsensus: Add pkg-config support 6 роки тому


Bitcoin Core integration/staging tree

Build Status


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.


Bitcoin Core 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/developer-notes.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 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

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.


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.