-------iBitHub (IBH)--------
integration/staging tree
================================
Copyright (c) 2009-2018 Bitcoin Developers
Copyright (c) 2011-2018 Litecoin Developers
Copyright (c) 2018 iBitHub Developers
What is Ibithub?
Ibithub is a new version of Bitcoin using scrypt as a proof-ofwork algorithm.
5 minute block targets
subsidy halves in 210k blocks (~2 years)
1.5MB Block hard limit
288 blocks to retarget difficulty
The rest is the same as Bitcoin.
50 coins per block
~21 million total coins For more information, as well as an immediately useable, binary version of the Ibithub client sofware,
see
https://www.ibithub.com
and download the wallet.
The wallet has a built-in miner. Once you are connected,
-Click "Help" on the toolbar
-Click "Debug Window"
-Click "Console"
-Type in "setgenerate true" to begin mining
-Typing "setgenerate false" will stop the miner
-Typing "getmininginfo" will show your stats.
License
Ibithub is released under the terms of the MIT license. See COPYING for more information or see r/http://opensource.org/licenses/MIT.
Development process
Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready. If it is a simple/trivial/non-controversial change, then one of the Ibithub development team members simply pulls it. If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion with the devs and community. The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/coding.txt) or are controversial. The master branch is regularly built and tested, but is not guaranteed to be completely stable. (https://github.com/ibithub/ibithub) are created regularly to indicate new official, stable release versions of Ibithub.
Testing
Testing and code review is the bottleneck for development; we get more pull requests than we can review and test. Please be patient and help out, 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 for the core code are in src/test/. To compile and run them: cd src; make -f makefile.unix test Unit tests for the GUI code are in src/qt/test/. To compile and run them: qmake BITCOIN_QT_TEST=1 -o Makefile.test bitcoin-qt.pro make -f Makefile.test ./ibithub-qt_test