AchillesSource
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.
build
contrib
doc
qa/rpc-tests
share
src We need this directory to exist for the compiling to work Feb 9, 2018
.gitattributes
Achilles-qt.pro This Jan 20, 2018
COPYING
INSTALL
Makefile
README.md
achilles-qt-windows.zip

README.md

Achilles integration/staging tree ================================http://achilles-wallet.website/ support@achilles-wallet.website

Copyright (c) 2009-2014 Bitcoin Developers Copyright (c) 2011-2014 Achilles Developers

What is Achilles?

Achilles is using scrypt as a proof-of-work algorithm.

  • 3 minute block targets
  • subsidy halves in 130625 blocks
  • 22000000 total coins

.

  • 80 coins per block
  • Coinbase maturity 20 blocks - Target spacing 3 minutes -Target timespan 15 minutes -Transaction confirmations 8 blocks.

For more information, as well as an immediately useable, binary version of the Achilles client sofware, see http://achilles-wallet.website/.

License

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

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