Skip to content
Cryptocurrency (PoW, Lyra2z) - Legacy Version
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Litecoin: Branding Dec 17, 2018
.tx tx: Update transifex slug 016x→017x Aug 2, 2018
build-aux macOS changes Mar 8, 2019
contrib update test seeds Apr 6, 2019
doc more cleanups Mar 8, 2019
share move to ACM Mar 8, 2019
src update test seeds Apr 6, 2019
test more cleanups Mar 8, 2019
tor updated Tor to v0.3.4.9 Dec 21, 2018
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore update .gitignore Mar 8, 2019
.travis.yml more cleanups Mar 8, 2019 initial commit May 26, 2018 move to ACM Mar 8, 2019
COPYING merge with upstream from litecoin 0.17-beta & fix conflicts Mar 7, 2019 merged updates Jun 13, 2018
LICENSE initial commit May 26, 2018 merge with upstream from litecoin 0.17-beta & fix conflicts Mar 7, 2019 updated Tor to v0.3.4.9 Dec 21, 2018 update Mar 7, 2019

Actinium Core integration/staging tree

What is Actinium?

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

For more information, as well as an immediately useable, binary version of the Actinium Core software, see


Actinium Core is released under the terms of the MIT license. See COPYING for more information or see

Development Process

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 Actinium Core.

The contribution workflow is described in

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #actinium-dev.


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. Further details on running and extending unit tests can be found in /src/test/

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/

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

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.


We only accept translation fixes that are submitted through Bitcoin Core's Transifex page. Translations are converted to Actinium periodically.

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.

You can’t perform that action at this time.