Skip to content
Bitcoin Core integration/staging tree
C++ Python C M4 Shell Objective-C Other
Branch: master
Clone or download
jonasschnelli Merge #16858: Qt: advise users not to switch wallets when opening a B…
…IP70 URI.

1153caf Qt: advise users not to switch wallets when opening a BIP70 URI. (James Hilliard)

Pull request description:

  It would probably be a good idea to have something like this before #15584 is merged.

ACKs for top commit:
  jonasschnelli:
    utACK 1153caf
  fanquake:
    ACK 1153caf

Tree-SHA512: 6e682dd280c44eaafb1206c32439df42a20173c33297bf93dd607f0a7a2faec8e2d17fff83c85027083ebd11a71795b443e707992251574370dd1d46b7bff060
Latest commit a40ccbb Sep 15, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github doc: Add issue templates for bug and feature request Sep 8, 2019
.tx gui: Update transifex slug for 0.19 Sep 2, 2019
build-aux/m4 doc: fix typo in bitcoin_qt.m4 comment Jul 24, 2019
build_msvc Added libbitcoin_qt and bitcoin-qt to the msbuild configuration. Sep 8, 2019
ci build: disable BIP70 support by default Sep 12, 2019
contrib Merge #16477: build: skip deploying plugins we dont use in macdeployq… Sep 10, 2019
depends Merge #16413: depends: Bump QT to LTS release 5.9.8 Sep 10, 2019
doc [wallet] Rename 'decode' argument in gettransaction method to 'verbose' Sep 13, 2019
share [qt] Change uninstall icon on Windows Aug 29, 2019
src Merge #16858: Qt: advise users not to switch wallets when opening a B… Sep 15, 2019
test [wallet] Rename 'decode' argument in gettransaction method to 'verbose' Sep 13, 2019
.appveyor.yml Added libbitcoin_qt and bitcoin-qt to the msbuild configuration. Sep 8, 2019
.cirrus.yml ci: Use ./ci/ on non-travis host Aug 15, 2019
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore Merge #16371: build: ignore macOS make deploy artefacts & add them to… Aug 21, 2019
.python-version .python-version: Specify full version 3.5.6 Mar 2, 2019
.style.yapf test: .style.yapf: Set column_limit=160 Mar 4, 2019
.travis.yml build: disable BIP70 support by default Sep 12, 2019
CONTRIBUTING.md doc: Update labels in CONTRIBUTING.md Aug 26, 2019
COPYING [Trivial] Update license year range to 2019 Dec 31, 2018
INSTALL.md Update INSTALL landing redirection notice for build instructions. Oct 5, 2016
Makefile.am build: ignore macOS make deploy artefacts & add them to clean-local Aug 14, 2019
README.md doc: Remove travis badge from readme Jun 19, 2019
SECURITY.md doc: Remove explicit mention of version from SECURITY.md Jun 14, 2019
autogen.sh Enable ShellCheck rules Jul 4, 2019
configure.ac build: disable BIP70 support by default Sep 12, 2019
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes Dec 14, 2015

README.md

Bitcoin Core integration/staging tree

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 and useful hints for developers can be found in doc/developer-notes.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.

You can’t perform that action at this time.