Skip to content

Commit

Permalink
Add files via upload
Browse files Browse the repository at this point in the history
  • Loading branch information
zoptaxapp committed May 15, 2019
1 parent d0255c0 commit b8c98a9
Showing 1 changed file with 52 additions and 0 deletions.
52 changes: 52 additions & 0 deletions README.md
@@ -0,0 +1,52 @@
# ZoptaxCoin
Zoptax Coin Source


Zoptax integration/staging tree
https://www.zoptax.com


What is ZoptaxCoin?
ZoptaxCoin is a lite version of Bitcoin using SHA256 as a proof-of-work (PoW/PoS) algorithm.

60 seconds block targets
~30 million total coins
50 coins per block
10 minutes blocks to retarget difficulty
For more information, as well as an immediately useable, binary version of the Zoptax client sofware, see https://www.zoptax.com

License
ZoptaxCoin 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 Zoptax 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 ZoptaxCoin.

Find Zoptax
Website: https://www.zoptax.com

Wallet: https://www.zoptax.com/windowswallet

Explorer: https://explorer.zoptax.com

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 zoptax-qt.pro
make -f Makefile.test
./zoptaxcoin-qt_test

0 comments on commit b8c98a9

Please sign in to comment.