No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
contrib .up Feb 28, 2017
doc .up Feb 28, 2017
qa/rpc-tests .up Feb 28, 2017
share .up Feb 28, 2017
src .up Feb 28, 2017
.gitattributes .up Feb 28, 2017
.gitignore .up Feb 28, 2017
ARGUSCOIN-qt.pro .up Feb 28, 2017
COPYING .up Feb 28, 2017
INSTALL .up Feb 28, 2017
README.md Update README.md Feb 28, 2017
arguscoin-qt.zip .up Feb 28, 2017

README.md

What is ARGUSCOIN?

Argus coin Bitcointalk Thread


https://bitcointalk.org/index.php?topic=1804278.0


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

Specifications

Algorithm :-Scrypt

Block halving :- 512000 blocks
Total coin supply:- 22.4 Million coins
18 coins per block
60 secs block target
Type PoW

Argus Foundation Fund
18% ( Premine )
RPC port - 10838
P2P port - 10837

License

ARGUSCOIN 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 ARGUSCOIN 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 ARGUSCOIN.

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