Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Latest commit d57cbac Mar 29, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux/m4 CobraX Mar 29, 2019
contrib CobraX Mar 29, 2019
depends CobraX Mar 29, 2019
doc CobraX Mar 29, 2019
share CobraX Mar 29, 2019
src new protocol version Mar 29, 2019
.cproject second Mar 29, 2019
.gitattributes second Mar 29, 2019
.gitignore second Mar 29, 2019
.project second Mar 29, 2019
.travis.yml second Mar 29, 2019
COPYING second Mar 29, 2019
INSTALL second Mar 29, 2019 second Mar 29, 2019

Commercial Photography


CobraX Coin – A Decentralized Data Sharing Platform, Hosting, and Content Distribution Network through Masternode Network.

Coin Specifications

| Specification | Value |
| NAME | CobraX |
| Block Size | 3MB |
| Block Time | 300s |
| PoW Reward | 10 CBRX |*
| Masternode Requirement | 1,000 CBRX |
| Port | 23777 |

| Block Reward Distribution |

10 CBRX per Block

| Masternode Reward |
| Block | Reward |
| 30% for Stakers | 70% of Block Reward for Masternodes |

Build cobrax Wallet

Building for 64-bit Windows

The first step is to install the mingw-w64 cross-compilation tool chain. Due to different Ubuntu packages for each distribution and problems with the Xenial packages the steps for each are different.

Common steps to install mingw32 cross compiler tool chain:

sudo apt install g++-mingw-w64-x86-64

Ubuntu Xenial 16.04 and Windows Subsystem for Linux

sudo apt install software-properties-common
sudo add-apt-repository "deb zesty universe"
sudo apt update
sudo apt upgrade
sudo update-alternatives --config x86_64-w64-mingw32-g++ # Set the default mingw32 g++ compiler option to posix.

Once the tool chain is installed the build steps are common:

Note that for WSL the cobrax Core source path MUST be somewhere in the default mount file system, for example /usr/src/cobrax, AND not under /mnt/d/. If this is not the case the dependency autoconf scripts will fail. This means you cannot use a directory that located directly on the host Windows file system to perform the build.

The next three steps are an example of how to acquire the source in an appropriate way.

cd /usr/src
sudo git clone
sudo chmod -R a+r+w cobrax

Once the source code is ready the build steps are below.

PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g') # strip out problematic Windows %PATH% imported var
cd depends
make HOST=x86_64-w64-mingw32 -j4
cd ..
./ # not required when building from tarball
./configure --prefix=`pwd`/depends/x86_64-w64-mingw32 --disable-tests
make HOST=x86_64-w64-mingw32 -j4

Build on Ubuntu

sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils git cmake libboost-all-dev
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:bitcoin/bitcoin
sudo apt-get update
sudo apt-get install libdb4.8-dev libdb4.8++-dev

# If you want to build the Qt GUI:
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler

git clone --recursive

cd cobrax

# Note autogen will prompt to install some more dependencies if needed
chmod a+x+w -R cobrax/
cd cobrax/

Build on OSX

The commands in this guide should be executed in a Terminal application. The built-in one is located in /Applications/Utilities/


Install the OS X command line tools:

xcode-select --install

When the popup appears, click Install.

Then install Homebrew.


brew install cmake automake berkeley-db4 libtool boost --c++11 --without-single --without-static miniupnpc openssl pkg-config protobuf qt5 libevent imagemagick --with-librsvg

NOTE: Building with Qt4 is still supported, however, could result in a broken UI. Building with Qt5 is recommended.

Build cobrax Core

  1. Clone the cobrax source code and cd into cobrax

     git clone --recursive
     cd cobrax
  2. Build cobrax Core:

    Configure and build the headless cobrax binaries as well as the GUI (if Qt is found).

    You can disable the GUI build by passing --without-gui to configure.

  3. It is recommended to build and run the unit tests:

    make check


Then you can either run the command-line daemon using src/cobraxd and src/cobrax-cli, or you can run the Qt GUI using src/qt/cobrax-qt

For in-depth description of Sparknet and how to use cobrax for interacting with contracts, please see sparknet-guide.


cobraxcore is GPLv3 licensed.

Development Process

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

The contribution workflow is described in


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. Further details on running and extending unit tests can be found in /src/test/

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.