mirror of https://github.com/bitcoin/bitcoin.git synced 2025-01-10 20:03:34 -03:00

Bitcoin Core mirror and no, I don't give a fuck about Monero.

bitcoin c-plus-plus cryptocurrency cryptography p2p

Find a file

fanquake 4241c193d4 Merge bitcoin/bitcoin#24134 : build: Fix zeromq package when cross-compiling `f13e642c83` build: Disable valgrind when building zeromq package in depends (Hennadii Stepanov) `b970f03bea` build: Disable libbsd when building zeromq package in depends (Hennadii Stepanov) `77899991b1` build: Update netbsd_kevent_void.patch (Hennadii Stepanov) Pull request description: Since v4.3.3 (`068385c951`) `libzmq` uses `libbsd` by default. This PR disables `libbsd` explicitly, as it's not a part of our depends. Zeromq will fallback to its internal `strlcpy` implementation. Otherwise, on systems with installed `libbsd-dev` package the `zeromq` package build system erroneously detects `libbsd` package from the host system: ```diff --- a/libzmq.pc +++ b/libzmq.pc @@ -8,5 +8,5 @@ Version: 4.3.4 Libs: -L${libdir} -lzmq Libs.private: -lpthread -Requires.private: +Requires.private: libbsd Cflags: -I${includedir} ``` This causes the `configure` fails to detect the `zeromq` package: ``` configure: WARNING: libzmq version 4.x or greater not found, disabling ``` --- Other minor improvements: - fixed `netbsd_kevent_void.patch` offset - disabled valgrind as it's used in unit tests which we do not run: ```diff --- a/zmq-configure-output +++ b/zmq-configure-output @@ -119,11 +119,6 @@ checking whether the g++ -m64 linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... (cached) GNU/Linux ld.so checking how to hardcode library paths into programs... immediate -checking for valgrind... valgrind -checking for Valgrind tool memcheck... memcheck -checking for Valgrind tool helgrind... helgrind -checking for Valgrind tool drd... drd -checking for Valgrind tool exp-sgcheck... exp-sgcheck checking linker version script flag... --version-script checking if version scripts can use complex wildcards... yes checking for working posix_memalign... yes ``` ACKs for top commit: fanquake: ACK `f13e642c83` Tree-SHA512: d4c86d4a841eb6e7c32157e84972243072f905496c2a4c14ec6f6ab4216df6695cbf29baa2233ce27eaede35d1e250ad2f9975b16f570d01509f0c5da4597cad		2022-01-27 10:44:48 +08:00
.github	doc: Remove label from good first issue template	2020-08-24 09:31:24 +02:00
.tx	qt: Bump transifex slug for 22.x	2021-04-21 13:46:41 +02:00
build-aux/m4	build: Drop redundant AC_SUBST macros	2021-12-29 23:14:45 +02:00
build_msvc	Merge bitcoin/bitcoin#23828 : scripted-diff: Rename libbitcoin_server.a to libbitcoin_node.a	2022-01-06 14:59:17 +01:00
ci	build: disable external signer on Windows	2022-01-15 10:02:04 +08:00
contrib	Merge bitcoin/bitcoin#23839 : Linux: build with and test for control flow instrumentation on x86_64	2022-01-25 16:01:21 +01:00
depends	Merge bitcoin/bitcoin#24134 : build: Fix zeromq package when cross-compiling	2022-01-27 10:44:48 +08:00
doc	transaction decoding infer output descriptors	2022-01-26 09:56:51 +08:00
share	scripted-diff: Bump copyright headers	2021-12-30 19:36:57 +02:00
src	Merge bitcoin/bitcoin#16795 : rpc: have raw transaction decoding infer output descriptors	2022-01-26 17:52:51 -05:00
test	Merge bitcoin/bitcoin#16795 : rpc: have raw transaction decoding infer output descriptors	2022-01-26 17:52:51 -05:00
.cirrus.yml	ci: Update Cirrus CI task name	2022-01-03 18:52:40 +02:00
.editorconfig	ci: Drop AppVeyor CI integration	2021-09-07 06:12:53 +03:00
.gitattributes	Separate protocol versioning from clientversion	2014-10-29 00:24:40 -04:00
.gitignore	build: use a static .tiff for macOS .dmg over generating	2022-01-02 15:38:19 +08:00
.python-version	Bump minimum python version to 3.6	2020-11-09 17:53:47 +10:00
.style.yapf	test: .style.yapf: Set column_limit=160	2019-03-04 18:28:13 -05:00
autogen.sh	scripted-diff: Bump copyright of files changed in 2019	2019-12-30 10:42:20 +13:00
configure.ac	build: disable external signer on Windows	2022-01-15 10:02:04 +08:00
CONTRIBUTING.md	Use the imperative mood in example subject line	2021-12-10 11:49:20 +11:00
COPYING	doc: Update license year range to 2022	2022-01-03 04:48:41 +08:00
INSTALL.md	doc: Added hyperlink for doc/build	2021-09-09 19:53:12 +05:30
libbitcoinconsensus.pc.in	build: remove libcrypto as internal dependency in libbitcoinconsensus.pc	2019-11-19 15:03:44 +01:00
Makefile.am	Merge bitcoin/bitcoin#23784 : bitcoin-tx: Require that input amount is provided for witness transactions	2022-01-05 17:48:55 +01:00
README.md	doc: Rework internal and external links	2021-02-17 09:18:46 +01:00
REVIEWERS	reviewers: add tracing	2022-01-05 17:22:49 -08:00
SECURITY.md	doc: Suggest `keys.openpgp.org` as keyserver in SECURITY.md	2021-11-08 12:22:04 +01:00

README.md

Bitcoin Core integration/staging tree

https://bitcoincore.org

For an immediately usable, binary version of the Bitcoin Core software, see https://bitcoincore.org/en/download/.

Further information about Bitcoin Core is available in the doc folder.

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 read the original Bitcoin 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 (see doc/build-*.md for instructions) and tested, but it is not guaranteed to be completely stable. Tags are created regularly from release branches to indicate new official, stable release versions of Bitcoin Core.

The https://github.com/bitcoin-core/gui repository is used exclusively for the development of the GUI. Its master branch is identical in all monotree repositories. Release branches and tags do not exist, so please do not fork that repository unless it is for development reasons.

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. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

The CI (Continuous Integration) systems make 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.