Skip to content
Tradecraft integration/staging tree
Branch: devel
Clone or download
Latest commit 6f0aa1e Mar 19, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx [Branding] Re-brand "bitcoin" -> "freicoin". Mar 19, 2019
build-aux/m4 [Branding] Re-brand "bitcoin" -> "freicoin". Mar 19, 2019
doc [Doc] Add release notes for v11.3. Mar 19, 2019
qa [Net] Change seed servers, and magic strings so as to avoid contact w… Mar 19, 2019
share [Branding] Qt: Replace logo with kria; change icons from blue -> gree… Mar 19, 2019
src [Release] v11.3-8698. Mar 19, 2019
.travis.yml [Branding] Re-brand "bitcoin" -> "freicoin". Mar 19, 2019
INSTALL [Branding] Re-brand "bitcoin" -> "freicoin". Mar 19, 2019 [Branding] Re-brand "bitcoin" -> "freicoin". Mar 19, 2019 [Branding] Re-brand "bitcoin" -> "freicoin". Mar 19, 2019
agpl-3.0.txt [License] Sublicense under the terms of the GNU Affero General Public… Mar 14, 2019 Bugfix: Replace bashisms with standard sh to fix build on non-BASH sy… Oct 3, 2014 [Release] v11.3-8698. Mar 19, 2019
mit-license.txt [License] Sublicense under the terms of the GNU Affero General Public… Mar 14, 2019

Freicoin integration/staging tree

Build Status

What is Freicoin?

Freicoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Freicoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Freicoin 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 Freicoin software, see


Freicoin is released under the conjunctive terms of BOTH version 3 of the GNU Affero General Public License as published by the Free Software Foundation AND the MIT software license. See COPYING for more information.

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 Freicoin 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/ 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 Freicoin.


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

Every pull request is built for both Windows and Linux on a dedicated server, and unit and sanity tests are automatically run. The binaries produced may be used for manual QA testing — a link to them will appear in a comment on the pull request posted by FreicoinPullTester. See for the build/test scripts.

Manual Quality Assurance (QA) Testing

Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code. See for how to create a test plan.


Changes to translations as well as new translations can be submitted to Freicoin'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 subscribe to the mailing list.

You can’t perform that action at this time.