BroFist!!!
BROFIST COIN - A COIN THAT YOU CAN MINE, RUN MASTERNODES AND SHOW TO YOUR MOM
This is the one that’s really gonna take off. Trust me. I am the most trustworthy Youtuber on the platform and I’m telling you right here, right now, BroFistCoin is where it’s at. We’re gonna BROFIIIIIIIIIIIIIIST to the TOP! This is the cryptocurrency that’s really gonna make it. It’s gonna be great.
Additional information, wallets, specifications & roadmap: http://brofistcoin.su/
BroFist Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.
The master branch is meant to be stable. Development is normally done in separate branches.
Tags are created to indicate new official,
stable release versions of BroFist Core.
The contribution workflow is described in CONTRIBUTING.md.
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.
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
There are also regression and integration tests of the RPC interface, written
in Python, that are run automatically on the build server.
These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py
The Travis CI system makes sure that every pull request is built for Windows and Linux, OS X, and that unit and sanity tests are automatically run.
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.