No description, website, or topics provided.
Switch branches/tags
Clone or download
Latest commit a33e124 Oct 8, 2018
Permalink
Failed to load latest commit information.
.github Test net sync'd fine; still needs new EXT keys Jan 12, 2018
.tx qt: Set transifex slug to 0.14 Jan 2, 2017
build-aux/m4 Explicitly search for bdb5.3. Jul 2, 2017
contrib add gpg key Mar 6, 2018
depends Test net sync'd fine; still needs new EXT keys Jan 12, 2018
doc gitian-build.sh specific example Mar 7, 2018
share Update installer images Mar 6, 2018
src nlr Oct 3, 2018
test nlr Oct 3, 2018
.autotools Test net sync'd fine; still needs new EXT keys Jan 12, 2018
.cproject key_tests updated Jan 18, 2018
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore all files converted to FLO 0.15.0.1rc, except for minor issues Jan 6, 2018
.project Test net sync'd fine; still needs new EXT keys Jan 12, 2018
.pydevproject Test net sync'd fine; still needs new EXT keys Jan 12, 2018
.travis.yml all files converted to FLO 0.15.0.1rc, except for minor issues Jan 6, 2018
CONTRIBUTING.md all files converted to FLO 0.15.0.1rc, except for minor issues Jan 6, 2018
COPYING [Trivial] Update license year range to 2017 Jan 23, 2017
INSTALL.md Update INSTALL landing redirection notice for build instructions. Oct 5, 2016
MacOSX10.11.sdk.tar.xz const changes for Mac build; chainparams to match witseg, MacOSX.xz f… Feb 21, 2018
Makefile.am all files converted to FLO 0.15.0.1rc, except for minor issues Jan 6, 2018
README.md all files converted to FLO 0.15.0.1rc, except for minor issues Jan 6, 2018
autogen.sh Test net sync'd fine; still needs new EXT keys Jan 12, 2018
configure.ac version bump Oct 8, 2018
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes Dec 14, 2015

README.md

FLO Core integration/staging tree

Build Status

https://flo.cash

What is FLO?

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

License

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

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/test_runner.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, 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.

Translations

We only accept translation fixes that are submitted through Bitcoin Core's Transifex page. Translations are converted to FLO 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.