Skip to content
FuturoCoin - the future of payments
C++ C Python M4 CSS Makefile Other
Branch: master
Clone or download
This branch is 13 commits ahead, 3706 commits behind dashpay:master.

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.


Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx Initial commit Jan 31, 2018
build-aux/m4 Initial commit Jan 31, 2018
contrib Initial commit Jan 31, 2018
depends Initial commit Jan 31, 2018
doc Update masternode configuration docs. Mar 25, 2020
futurocoin-docs Initial commit Jan 31, 2018
qa Initial commit Jan 31, 2018
share FTO fork update. Mar 12, 2020
src Remove unused constants and change values of masternode payment required Mar 18, 2020
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore update gitignore Apr 17, 2016
.travis.yml Initial commit Jan 31, 2018 Initial commit Jan 31, 2018
COPYING Initial commit Jan 31, 2018
INSTALL Initial commit Jan 31, 2018 Initial commit Jan 31, 2018 Bugfix: Replace bashisms with standard sh to fix build on non-BASH sy… Oct 3, 2014 FTO fork update. Mar 12, 2020 Initial commit Jan 31, 2018

Futuro Core staging tree 0.1

What is FuturoCoin?

FuturoCoin is a new digital cryptocurrency that is created to guarantee instant payments to anyone, anywhere in the world with the constant transaction fees at the competing level. FuturoCoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Futuro 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 Futuro core software, see


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

Development Process

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


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/

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.

You can’t perform that action at this time.