#bitcoin #ai # urban-doodle *#1
- 🆒 #relaxing #beat 😁☑️✅✅✅✅✅✅✅✅
- dobar Skip to content
You have unread notifications Code Issues 347 Pull requests 285 Projects 5 Security Insights Notification settings Fork your own copy of bitcoin/bitcoin Star this repository Bitcoin Core integration/staging tree
bitcoincore.org/en/download License MIT license Security policy Security policy 70.2k stars 35.1k forks 3.9k watching Activity Public repository bitcoin/bitcoin Branches Tags Latest commit @fanquake fanquake … 1 hour ago Git stats Files 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/.
What is Bitcoin Core? Bitcoin Core connects to the Bitcoin peer-to-peer network to download and fully validate blocks and transactions. It also includes a wallet and graphical user interface, which can be optionally built.
Further information about Bitcoin Core is available in the doc folder.
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.
Releases 438 Bitcoin Core 25.0 Latest on May 26
- 42 releases Contributors 914 @laanwj @fanquake @sipa @hebasto @achow101 @gavinandresen @jnewbery @jonasschnelli @practicalswift @jonatack @theuni
- 903 contributors Languages C++ 65.2%
Python 19.5%
C 10.9%
M4 1.3%
Shell 1.0%
Makefile 0.9%
Other 1.2% Footer © 2023 GitHub, Inc. Footer navigation Terms Privacy Security Status Docs Contact GitHub Pricing API Training Blog About Copied text @"217 you look 🌟
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent