Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Bongger integration/staging tree

Copyright (c) 2009-2013 Bitcoin Developers Copyright (c) 2011-2013 Litecoin Developers Copyright (c) 2011-2014 Bongger Developers

What is Bongger?

Bongger is a lite version of Bitcoin using scrypt as a proof-of-work algorithm.

Algo:  Scrypt
RPC Port: 7070
P2P Port: 7071 
Rewards per block: 420 Coins 
Target per block: 42 Seconds  
Halving: Every 500,001 Blocks 
Total Number of Coins: 504,000,000 
84,000,000 Coins premine to distributed to users,miners and as bounties! 
420,000,000 Coins left for mining
block confirmations:  3

For more information, as well as an immediately useable, binary version of the Bongger client sofware, see


Bongger is released under the terms of the MIT license. See COPYING for more information or see

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 Bongger 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 (if they haven't already) on the mailing list.

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. Tags are created regularly to indicate new official, stable release versions of Bongger.


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
make -f Makefile.test


Bongger Crypto Coin Wallet Soure Code







No releases published


No packages published