Franko source tree
C++ C Python Makefile HTML Shell Other
Pull request Compare This branch is 149 commits ahead, 7633 commits behind litecoin-project:master.
Latest commit 9221673 Nov 12, 2015 @franko-org update permissions
Permalink
Failed to load latest commit information.
.tx commit uno ⛅️ Jun 16, 2015
build-aux/m4 commit uno ⛅️ Jun 16, 2015
contrib removed extra file and updated makefile.am Jun 19, 2015
depends
doc
qa commit uno ⛅️ Jun 16, 2015
share smh Jun 19, 2015
src Merge pull request #5 from franko-org/frk-0.10.2 Sep 23, 2015
.gitattributes commit uno ⛅️ Jun 16, 2015
.gitignore
.travis.yml commit uno ⛅️ Jun 16, 2015
COPYING commit uno ⛅️ Jun 16, 2015
INSTALL commit uno ⛅️ Jun 16, 2015
Makefile.am commit uno ⛅️ Jun 16, 2015
README.md
autogen.sh update permissions Nov 12, 2015
bitcoin-qt.pro number bumps and checkpoint Jun 19, 2014
configure.ac
pkg.m4 commit uno ⛅️ Jun 16, 2015

README.md

Franko integration/staging tree

http://www.frankos.org

Copyright (c) 2009-2013 Bitcoin Developers Copyright (c) 2011-2013 Litecoin Developers Copyright (c) 2012-2013 Franko Developers

What is Franko?

Franko is anonymous internet money that can be instantly transferred to anyone in the world over a public peer-to-peer network ran by volunteers .

  • 30 second transaction times
  • coin creation halves in 22m blocks (~22 years)
  • ~11 million total coins
  • 0.25 coins created per block discovered
  • 720 blocks to retarget difficulty

For more information, as well as an immediately useable, binary version of the Franko client sofware, see http://www.frankos.org.

License

Franko is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.

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 Franko 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/coding.txt) 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 Franko.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test. Please be patient and help out, 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 for the core code are in src/test/. To compile and run them:

cd src; make -f makefile.unix test

Unit tests for the GUI code are in src/qt/test/. To compile and run them:

qmake BITCOIN_QT_TEST=1 -o Makefile.test bitcoin-qt.pro
make -f Makefile.test
./franko-qt_test