Skip to content

Latest commit

 

History

History
75 lines (52 loc) · 2.47 KB

README.md

File metadata and controls

75 lines (52 loc) · 2.47 KB
Raw

PepeGold integration/staging tree

http://www.pepegold.org

Copyright (c) 2009-2014 Bitcoin Developers Copyright (c) 2011-2018 PepeGold Developers

What is PepeGold?

PepeGold is a lite version of Bitcoin using scrypt as a proof-of-work algorithm along with Proof-of-stake at 50% annual stake interest.

  • 1 minute block targets
  • maximum PoW blocks are 10,000
  • Proof of stake interest rate 50% per year
  • Minimum coin age for stake is 8 hours
  • ~26 million total coins

The rest is the same as Bitcoin.

  • 50 coins per block
  • Every new block to retarget difficulty

For more information, as well as an immediately useable, binary version of the PepeGold client sofware, see http://www.pepegold.org.

License

PepeGold is released under the terms of the MIT license. See COPYING for more information or see 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 PepeGold 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. Tags are created regularly to indicate new official, stable release versions of PepeGold.

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
./pepegold-qt_test