Switch branches/tags
Nothing to show
Clone or download
ulacoin Initial commit
Latest commit c715c29 Aug 21, 2017
Failed to load latest commit information.
build UlaTech ULA Aug 21, 2017
contrib UlaTech ULA Aug 21, 2017
doc UlaTech ULA Aug 21, 2017
qa/rpc-tests UlaTech ULA Aug 21, 2017
share UlaTech ULA Aug 21, 2017
src UlaTech ULA Aug 21, 2017
.gitattributes Initial commit Aug 21, 2017
.gitignore Initial commit Aug 21, 2017
COPYING UlaTech ULA Aug 21, 2017
INSTALL UlaTech ULA Aug 21, 2017
LICENSE Initial commit Aug 21, 2017
Makefile UlaTech ULA Aug 21, 2017
README.md Initial commit Aug 21, 2017
UlaTech-qt.pro UlaTech ULA Aug 21, 2017


UlaTech integration/staging tree


Copyright (c) 2009-2014 Bitcoin Developers Copyright (c) 2011-2014 UlaTech Developers

What is UlaTech?

UlaTech is a lite version of Bitcoin using scrypt as a proof-of-work algorithm.

  • 5 minute block targets
  • subsidy halves in 720000 blocks (~4 years)
  • ~90 million total coins

The rest is the same as Bitcoin.

  • 25 coins per block
  • 2016 blocks to retarget difficulty

For more information, as well as an immediately useable, binary version of the UlaTech client sofware, see http://www.ulatech.com.


UlaTech 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 UlaTech 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 with the devs and community.

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 UlaTech.


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