Skip to content


Repository files navigation

GreenCoin integration/staging tree

Copyright (c) 2009-2018 GreenCoin Developers

What is GreenCoin?

GreenCoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. GreenCoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. GreenCoin is also 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 GreenCoin client software, see


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

For desktop Windows or Ubuntu use qt version of wallet

Windows -

Linux\Ubuntu -

How to compile daemon node on Ubuntu 16.04

Use the following instructions

Update your Ubuntu machine.

sudo apt-get update
sudo apt-get upgrade

Install the dependencies to compile from source code.

sudo apt-get install build-essential libssl-dev libdb-dev libdb++-dev libboost-dev git libssl1.0.0-dbg
sudo apt-get install libdb-dev libdb++-dev libboost-all-dev libminiupnpc-dev libminiupnpc-dev libevent-dev libcrypto++-dev libgmp3-dev

Create a directory for the source code.

git clone

Go to the src directory of your source code.

mv GreenCoin source_code
cd source_code/src
mkdir obj

Execute the following command to compile the daemon.

make -f makefile.unix RELEASE=1

The compiling will take about 30 minutes depending on your system. Required 2GB+ of RAM memory

Your compiled daemon named greencoind can be found in the src folder when compiling is finished.

Installation of daemon

On Ubuntu 16.04 Move compiled daemon to your Home folder and follow instruction

mv greencoind $HOME

On Ubuntu 14.04 You do not need compile daemon, just download and untar

tar -xzvf greencoin-daemon-linux.tar.gz

Install the daemon.

chmod +x greencoind
sudo mv greencoind /usr/bin/

Create the config file.

mkdir $HOME/.greencoin
nano $HOME/.greencoin/greencoin.conf

Paste the following lines in greencoin.conf.


Start your node with the following command.


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 GreenCoin 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/ 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 GreenCoin.


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
make -f Makefile.test

Every pull request is built for both Windows and Linux on a dedicated server, and unit and sanity tests are automatically run. The binaries produced may be used for manual QA testing — a link to them will appear in a comment on the pull request posted by GreenCoinPullTester. See for the build/test scripts.

Manual Quality Assurance (QA) Testing

Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code.

See for how to create a test plan.