Official source code ARC
C++ C Python M4 Makefile HTML Other
Clone or download
Latest commit 1321e72 Aug 12, 2017
Permalink
Failed to load latest commit information.
.tx upgrade Feb 14, 2017
build-aux/m4 upgrade Feb 14, 2017
contrib 12.01.02 Mar 4, 2017
depends 12.01.02 Mar 4, 2017
doc 12.01.02 Mar 4, 2017
qa 12.01.02 Mar 4, 2017
share 12.01.02 Mar 4, 2017
src css Mar 6, 2017
.gitattributes upgrade Feb 14, 2017
.gitignore 12.01.02 Mar 4, 2017
.travis.yml 12.01.02 Mar 4, 2017
Arctic Coin Roadmap.png Add files via upload Aug 12, 2017
CONTRIBUTING.md upgrade Feb 14, 2017
COPYING 12.01.02 Mar 4, 2017
INSTALL upgrade Feb 14, 2017
Makefile.am upgrade Feb 14, 2017
README.md Update README.md Mar 4, 2017
autogen.sh first commit Aug 22, 2016
configure.ac 12.01.02 Mar 4, 2017
libbitcoinconsensus.pc.in upgrade Feb 14, 2017

README.md

Arctic Core staging tree 0.12.1

https://www.arcticcoin.org

What is Arctic?

Arctic is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. Arctic uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Arctic Core is the name of the open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Arctic Core software, see https://www.arcticcoin.org/get-arcticcoin/.

License

Arctic Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The goldmine branch is meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of Arctic Core.

The contribution workflow is described in CONTRIBUTING.md.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, 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 can be compiled and run (assuming they weren't disabled in configure) with: make check

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

The Travis CI system makes sure that every pull request is built for Windows and Linux, OS X, and that unit and sanity tests are automatically run.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

Translations

Changes to translations as well as new translations can be submitted to Arctic Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also follow the forum.