XTRI: Monero based privacy digital asset focusing on eSports
Branch: master
Clone or download
Pull request Compare This branch is 244 commits ahead, 572 commits behind monero-project:master.
Type Name Latest commit message Commit time
Failed to load latest commit information.
cmake Fix Syncing issues Nov 3, 2018
contrib Fix get_next_difficulty_for_alternative_chain Nov 8, 2018
external Merge pull request monero-project#4471 Oct 2, 2018
include Update 2018 copyright Jan 26, 2018
src Merge remote-tracking branch 'origin/master' Feb 14, 2019
translations Finish all contexts but simple_wallet, translate 23% of simple_wallet Oct 30, 2018
utils Merge pull request monero-project#4517 Oct 9, 2018
.gitattributes cmake: support git info in released tarballs Oct 23, 2014
.gitmodules rapidjson: remove outdated in-tree, use submodule May 25, 2018
.travis.yml Remove Travis check in depends toolchain file Oct 30, 2018
CMakeLists_IOS.txt Readd copyright starting date Jan 26, 2018
Dockerfile Dockerfile: init and update submodules Oct 14, 2018
Doxyfile Changed URLs to HTTPS Jun 23, 2018
Makefile Makefile: fix building without a git tree Oct 30, 2018
README.i18n.md Updating Qt download link Aug 7, 2018
README.md Update README.md Feb 11, 2019



Image of Triton Freedom for Streamers and Professional Gamers

Project Triton [XTRI] is developing innovative donation platforms for the Online Streaming and ESports industries through blockchain technology

For announcements:




A new journey for Project Triton. The SAO stablecoin. SAO is a decentralized stablecoin based on mint and burn protocol called the Sao Dollar (SAO), which is minted from our established volatile coin Triton (XTRI).

Check out the announcement here
Check out the paper here

General Information

Copyright (c) 2014-2018 The Monero Project.
Copyright (c) 2018 Project Triton. Portions Copyright (c) 2012-2013 The Cryptonote developers.

Current maintainer

  • Harrison Hesslink (krakn)

Anyone is welcome to contribute to Triton's codebase! If you have a fix or code change, feel free to submit it as a pull request directly to the "master" branch. In cases where the change is relatively small or does not affect other parts of the codebase it may be merged in immediately by any one of the collaborators. On the other hand, if the change is particularly large or complex, it is expected that it will be discussed at length either well in advance of the pull request being submitted, or even directly on the pull request.



If you want to help out, see CONTRIBUTING for a set of guidelines.

Compiling Triton from source


The following table summarizes the tools and libraries required to build. A few of the libraries are also included in this repository (marked as "Vendored"). By default, the build uses the library installed on the system, and ignores the vendored sources. However, if no library is found installed on the system, then the vendored source will be built and used. The vendored sources are also used for statically-linked builds because distribution packages often include only shared library binaries (.so) but not static library archives (.a).

Dep Min. version Vendored Debian/Ubuntu pkg Arch pkg Fedora Optional Purpose
GCC 4.7.3 NO build-essential base-devel gcc NO
CMake 3.5 NO cmake cmake cmake NO
pkg-config any NO pkg-config base-devel pkgconf NO
Boost 1.58 NO libboost-all-dev boost boost-devel NO C++ libraries
OpenSSL basically any NO libssl-dev openssl openssl-devel NO sha256 sum
libzmq 3.0.0 NO libzmq3-dev zeromq cppzmq-devel NO ZeroMQ library
OpenPGM ? NO libpgm-dev libpgm openpgm-devel NO For ZeroMQ
libnorm[2] ? NO libnorm-dev ` YES For ZeroMQ
libunbound 1.4.16 YES libunbound-dev unbound unbound-devel NO DNS resolver
libsodium ? NO libsodium-dev libsodium libsodium-devel NO cryptography
libunwind any NO libunwind8-dev libunwind libunwind-devel YES Stack traces
liblzma any NO liblzma-dev xz xz-devel YES For libunwind
libreadline 6.3.0 NO libreadline6-dev readline readline-devel YES Input editing
ldns 1.6.17 NO libldns-dev ldns ldns-devel YES SSL toolkit
expat 1.1 NO libexpat1-dev expat expat-devel YES XML parsing
GTest 1.5 YES libgtest-dev[1] gtest gtest-devel YES Test suite
Doxygen any NO doxygen doxygen doxygen YES Documentation
Graphviz any NO graphviz graphviz graphviz YES Documentation

[1] On Debian/Ubuntu libgtest-dev only includes sources and headers. You must build the library binary manually. This can be done with the following command sudo apt-get install libgtest-dev && cd /usr/src/gtest && sudo cmake . && sudo make && sudo mv libg* /usr/lib/ [2] libnorm-dev is needed if your zmq library was built with libnorm, and not needed otherwise

Debian / Ubuntu one liner for all dependencies
sudo apt update && sudo apt install build-essential cmake pkg-config libboost-all-dev libssl-dev libzmq3-dev libunbound-dev libsodium-dev libunwind8-dev liblzma-dev libreadline6-dev libldns-dev libexpat1-dev doxygen graphviz libpgm-dev

Cloning the repository

Clone recursively to pull-in needed submodule(s):

$ git clone --recursive https://github.com/TritonNetwork/TritonProtocol triton

If you already have a repo cloned, initialize and update:

$ cd triton && git submodule init && git submodule update

Build instructions

Monero uses the CMake build system and a top-level Makefile that invokes cmake commands as needed.

On Linux and OS X

  • Install the dependencies

  • Change to the root of the source code directory, change to the most recent release branch, and build:

      cd triton
      git checkout v3.0.0

    Optional: If your machine has several cores and enough memory, enable parallel build by running make -j<number of threads> instead of make. For this to be worthwhile, the machine should have one core and about 2GB of RAM available per thread.

    Note: If cmake can not find zmq.hpp file on OS X, installing zmq.hpp from https://github.com/zeromq/cppzmq to /usr/local/include should fix that error.

    Note: The instructions above will compile the most stable release of the Monero software. If you would like to use and test the most recent software, use git checkout master. The master branch may contain updates that are both unstable and incompatible with release software, though testing is always encouraged.

  • The resulting executables can be found in build/release/bin

  • Add PATH="$PATH:$HOME/monero/build/release/bin" to .profile

  • Run Monero with monerod --detach

  • Optional: build and run the test suite to verify the binaries:

      make release-test

    NOTE: core_tests test may take a few hours to complete.

  • Optional: to build binaries suitable for debugging:

       make debug
  • Optional: to build statically-linked binaries:

       make release-static

Dependencies need to be built with -fPIC. Static libraries usually aren't, so you may have to build them yourself with -fPIC. Refer to their documentation for how to build them.

  • Optional: build documentation in doc/html (omit HAVE_DOT=YES if graphviz is not installed):

      HAVE_DOT=YES doxygen Doxyfile

On Windows:

Binaries for Windows are built on Windows using the MinGW toolchain within MSYS2 environment. The MSYS2 environment emulates a POSIX system. The toolchain runs within the environment and cross-compiles binaries that can run outside of the environment as a regular Windows application.

Preparing the build environment

  • Download and install the MSYS2 installer, either the 64-bit or the 32-bit package, depending on your system.

  • Open the MSYS shell via the MSYS2 Shell shortcut

  • Update packages using pacman:

      pacman -Syuu  
  • Exit the MSYS shell using Alt+F4

  • Edit the properties for the MSYS2 Shell shortcut changing "msys2_shell.bat" to "msys2_shell.cmd -mingw64" for 64-bit builds or "msys2_shell.cmd -mingw32" for 32-bit builds

  • Restart MSYS shell via modified shortcut and update packages again using pacman:

      pacman -Syuu  
  • Install dependencies:

    To build for 64-bit Windows:

      pacman -S mingw-w64-x86_64-toolchain make mingw-w64-x86_64-cmake mingw-w64-x86_64-boost mingw-w64-x86_64-openssl mingw-w64-x86_64-zeromq mingw-w64-x86_64-libsodium mingw-w64-x86_64-hidapi

    To build for 32-bit Windows:

      pacman -S mingw-w64-i686-toolchain make mingw-w64-i686-cmake mingw-w64-i686-boost mingw-w64-i686-openssl mingw-w64-i686-zeromq mingw-w64-i686-libsodium mingw-w64-i686-hidapi
  • Open the MingW shell via MinGW-w64-Win64 Shell shortcut on 64-bit Windows or MinGW-w64-Win64 Shell shortcut on 32-bit Windows. Note that if you are running 64-bit Windows, you will have both 64-bit and 32-bit MinGW shells.


  • To git clone, run:

      git clone --recursive https://github.com/TritonNetwork/TritonProtocol.git triton


  • Change to the cloned directory, run:

      cd triton
      git checkout v3.0.0
  • If you are on a 64-bit system, run:

      make release-static-win64
  • If you are on a 32-bit system, run:

      make release-static-win32
  • The resulting executables can be found in build/release/bin

  • Optional: to build Windows binaries suitable for debugging on a 64-bit system, run:

      make debug-static-win64
  • Optional: to build Windows binaries suitable for debugging on a 32-bit system, run:

      make debug-static-win32
  • The resulting executables can be found in build/debug/bin