README.md BridgeCoin software integration/staging tree What is BridgeCoin? BridgeCoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Bridgecoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. BridgeCoin 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 BridgeCoin software, see.

How to Mine Ethereum - A Beginner's Guide. It also passes information to the mining software. Now you know the basics on how to mine Ethereum on your Windows PC. BridgeCoin Specification mining algorithm. 3344 for high diff mining) Where to buy/trade BCO. Altcoin to fund the development of a software platform: BridgeCoin.

License BridgeCoin software is released under the terms of the MIT license. See for more information or see.

Development Process The master branch is regularly built and tested, but is not guaranteed to be completely stable. Are created regularly to indicate new official, stable release versions of BridgeCoin software. The contribution workflow is described in. The developer should be used to discuss complicated or controversial changes before working on a patch set. Developer IRC can be found on Freenode at #bridgecoin-dev. How Much Money Can I Make With Viacoin VIA Mining here.

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 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 There are also of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the are installed) with: qa/pull-tester/rpc-tests.py The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, 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 We only accept translation fixes that are submitted through. Translations are converted to BridgeCoin periodically. Translations are periodically pulled from Transifex and merged into the git repository. See the 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.