Created: 2014-05-19 08:50
Updated: 2014-07-05 00:25

StabilityShares development tree

StabilityShares is a PoS-based cryptocurrency.

Ubuntu Dependencies

sudo apt-get install build-essential libboost-all-dev libcurl4-openssl-dev libdb4.8-dev libdb4.8++-dev git qt-sdk libminiupnpc-dev

sudo apt-get install qrencode libqrencode-dev

Qt v4.8.5 is what we used to compile StabilityShares.

Compiling daemon on ubuntu

cd ~

git clone git://

cd stabilitysharesxsi/src

chmod 777 ./leveldb/build_detect_platform

make -f makefile.unix USE_UPNP=-

sudo cp stabilitysharesxsid /usr/bin

When trying to compile if you get this error: "../share/ 34: ../share/ cannot create obj/build.h: Directory nonexistent make: *** [obj/build.h] Error "

Make sure to create the folder "obj" in the "src" folder:

cd stabilityshares/src

If Root: cd ~stabilityshares/src

mkdir obj

Then try compiling again.

Compiling QT Wallet on ubuntu

git clone git://

cd stabilitysharesxsi

chmod 777 ./src/leveldb/build_detect_platform

qmake "USE_UPNP=-"


Use make clean first if you have already built the daemon



Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

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 they don't match the project's coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new stable release versions of StabilityShares.

Feature branches are created when there are major new features being worked on by several people.

From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'.

Cookies help us deliver our services. By using our services, you agree to our use of cookies Learn more