Litecoin Core integration/staging tree
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
Chun Kuan Lee 99d33a6bec
appveyor: Script improvement part II
6 years ago
.github doc: Add GitHub pr template 6 years ago
.travis Enable functional tests in UBSAN job. Enable -fsanitize=integer (part of UBSAN). Merge UBSAN Travis job with no depends. 6 years ago
.tx tx: Update transifex slug 016x→017x 6 years ago
build-aux/m4 Merge #13095: build: update ax_boost_chrono/unit_test_framework 6 years ago
build_msvc scripted-diff: Move util files to separate directory. 6 years ago
contrib Enable functional tests in UBSAN job. Enable -fsanitize=integer (part of UBSAN). Merge UBSAN Travis job with no depends. 6 years ago
depends build: Remove illegal spacing in darwin.mk 6 years ago
doc Merge #14060: ZMQ: add options to configure outbound message high water mark, aka SNDHWM 6 years ago
share gui: explicitly disable "Dark Mode" appearance on macOS 6 years ago
src trivial: Don't translate in help text 6 years ago
test example_test.py: fixup coinbase height argument, derive number clearly 6 years ago
.appveyor.yml appveyor: Script improvement part II 6 years ago
.gitattributes Separate protocol versioning from clientversion 10 years ago
.gitignore gitignore contents of db4 folder 6 years ago
.travis.yml Enable functional tests in UBSAN job. Enable -fsanitize=integer (part of UBSAN). Merge UBSAN Travis job with no depends. 6 years ago
CONTRIBUTING.md added details about commit messages 6 years ago
COPYING [Trivial] Update license year range to 2018 7 years ago
INSTALL.md Update INSTALL landing redirection notice for build instructions. 8 years ago
Makefile.am Merge #14253: Build: during 'make clean', remove some files that are currently missed. 6 years ago
README.md doc: Adjust bitcoincore.org links 6 years ago
autogen.sh Add "export LC_ALL=C" to all shell scripts 6 years ago
configure.ac build: Add --disable-bip70 configure option 6 years ago
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes 9 years ago

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

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. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

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