BitcoinX is a cryptocurrency, a virtual currency designed to act as money and a form of payment outside the control of any one person, group, or entity, thus removing the need for third-party involvement in financial transactions. It is rewarded to blockchain miners for the work done to verify transactions and can be purchased on several exchanges.

BitcoinX was introduced to the public in 2009 by an anonymous developer or group of developers using the name Satoshi Nakamoto.

It has since become the most well-known cryptocurrency in the world. Its popularity has inspired the development of many other cryptocurrencies. These competitors either attempt to replace it as a payment system or are used as utility or security tokens in other blockchains and emerging financial technologies.

Learn more about the cryptocurrency that started it all—the history behind it, how it works, how to get it, and what it can be used for murim rpg simulation wiki.

For more information as well as a ready-to-use, binary version of the Bitcoin evolution.


BitcoinX 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 BitcoinX Core.

The contribution workflow is described in CONTRIBUTING.md.


Testing and code review are bottlenecks to development. We receive more pull requests than we can review and test on short notice. Please be patient and help by checking other people’s pull requests, and remember that this is a security-critical project where any mistakes can cost people a lot of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code and submit new unit tests for old code. Unit tests can be compiled and run (assuming they were not disabled in the configure) with: check More 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, which 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 ensures that each pull request is built for Windows, Linux, and OS X, and that unit/contests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by someone other than the developer who wrote the code. This is especially important for large or high-risk changes. Adding a test plan to the pull request description is useful if testing the changes is not straightforward murim login wiki

Leave a Reply

Your email address will not be published. Required fields are marked *