選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。
fanquake 282abd8358
[build-aux] Boost_Base serial 27
5年前
.github [Doc] Improve GitHub issue template 5年前
.tx tx: change slug to `bitcoin.qt-translation-013x` 5年前
build-aux/m4 [build-aux] Boost_Base serial 27 5年前
contrib Merge #8249: Enable (and check for) 64-bit ASLR on Windows 5年前
depends Merge #8819: [depends] Boost 1.61.0 5年前
doc Merge #8892: doc: Add build instructions for FreeBSD 5年前
qa Merge #8904: [qa] Fix compact block shortids for a test case 5年前
share Merge #8784: Copyright headers for build scripts 5年前
src Merge #8817: update bitcoin-tx to output witness data 5年前
.gitattributes Separate protocol versioning from clientversion 7年前
.gitignore gitignore: Remove unused lines 5年前
.travis.yml [travis] cross-mac: explicitly enable gui 5年前
CONTRIBUTING.md Merge #8771: CONTRIBUTING: Mention not to open several pulls 5年前
COPYING Update license year range to 2016 5年前
INSTALL.md Update INSTALL landing redirection notice for build instructions. 5年前
Makefile.am Add MIT license to Makefiles 5年前
README.md readme: Omit phrasing; 'new' 5年前
autogen.sh Add MIT license to autogen.sh and share/genbuild.sh 5年前
configure.ac Merge #8813: bitcoind: Daemonize using daemon(3) 5年前
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes 5年前

README.md

Bitcoin Core integration/staging tree

Build Status

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://bitcoin.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.

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 (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, 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.