Enhanced FLO wallet with new coin control features added by Ranchi Mall team.

Go to file

Jeremiah Buddenhagen 71f935e79c Update installer images		2018-03-06 14:01:34 -08:00
.github	Test net sync'd fine; still needs new EXT keys	2018-01-11 19:21:07 -05:00
.tx	qt: Set transifex slug to 0.14	2017-01-02 09:36:03 +01:00
build-aux/m4	Explicitly search for bdb5.3.	2017-07-02 02:48:00 +00:00
contrib	add gpg key	2018-03-06 12:03:04 -08:00
depends	Test net sync'd fine; still needs new EXT keys	2018-01-11 19:21:07 -05:00
doc	Mac sdk gz -> xz	2018-03-05 16:41:09 -08:00
share	Update installer images	2018-03-06 14:01:34 -08:00
src	testnet dns seed	2018-03-05 16:44:48 -08:00
test	prefer camelCase FloData	2018-02-11 12:28:37 -08:00
.autotools	Test net sync'd fine; still needs new EXT keys	2018-01-11 19:21:07 -05:00
.cproject	key_tests updated	2018-01-18 14:45:18 -05:00
.gitattributes	Separate protocol versioning from clientversion	2014-10-29 00:24:40 -04:00
.gitignore	all files converted to FLO 0.15.0.1rc, except for minor issues	2018-01-06 15:26:19 -05:00
.project	Test net sync'd fine; still needs new EXT keys	2018-01-11 19:21:07 -05:00
.pydevproject	Test net sync'd fine; still needs new EXT keys	2018-01-11 19:21:07 -05:00
.travis.yml	all files converted to FLO 0.15.0.1rc, except for minor issues	2018-01-06 15:26:19 -05:00
autogen.sh	Test net sync'd fine; still needs new EXT keys	2018-01-11 19:21:07 -05:00
configure.ac	all files converted to FLO 0.15.0.1rc, except for minor issues	2018-01-06 15:26:19 -05:00
CONTRIBUTING.md	all files converted to FLO 0.15.0.1rc, except for minor issues	2018-01-06 15:26:19 -05:00
COPYING	[Trivial] Update license year range to 2017	2017-01-23 23:46:06 +01:00
INSTALL.md	Update INSTALL landing redirection notice for build instructions.	2016-10-06 12:27:23 +13:00
libbitcoinconsensus.pc.in	Unify package name to as few places as possible without major changes	2015-12-14 02:11:10 +00:00
MacOSX10.11.sdk.tar.xz	const changes for Mac build; chainparams to match witseg, MacOSX.xz file for gitian build	2018-02-21 14:33:47 -05:00
Makefile.am	all files converted to FLO 0.15.0.1rc, except for minor issues	2018-01-06 15:26:19 -05:00
README.md	all files converted to FLO 0.15.0.1rc, except for minor issues	2018-01-06 15:26:19 -05:00

README.md

FLO Core integration/staging tree

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.