Branch: master
Clone or download


Build Status Stories in Ready

Graph on Pull Request History

Throughput Graph

Dynamic (DYN) v2.3.5.0

DYN logo

Copyright (c) 2016-2018 Duality Blockchain Solutions

What is Dynamic?

  • Coin Suffix: DYN
  • PoW Mining Algorithm: Argon2d
  • PoW Difficulty Algorithm: Digishield V3
  • PoW Period: Unlimited
  • PoW Target Spacing: 128 Seconds
  • PoW Reward per Block: Controlled via Fluid Protocol
  • PoW Reward Start Height: Block 5,137
  • Maturity: 10 Blocks
  • PoW Blocks: ~675 per day
  • Dynode Collateral Amount: 1000 DYN
  • Dynode Min Confirmation: 17 Blocks
  • Dynode Reward: Controlled via Fluid Protocol
  • Dynode Reward Start Height: Block 10,273
  • Total Coins: 263 - 1
  • Min TX Fee: 0.0001 DYN

Dynamic(DYN) is Duality’s tokenized-currency provided with supply elasticity to ensure price stability for day to day transactions of end-users. Duality uses company proceeds to place buy back orders on the Dynamic(DYN) market to keep inflation within acceptable bounds.

Dynamic(DYN) lays the groundwork for offering BaaS(Blockchain as a Service) by hosting a multitude of second tier nodes called Dynodes. Rewards can be adjusted through the 'Fluid Protocol' created by Duality to adjust to a maturing market.

As a modern currency Dynamic(DYN) will be actively maintained to keep up with the latest market trends. Dynamic(DYN) features fast and InstantSend transactions at an affordable rate, also end-users that care for consumer privacy are able to anonymously transact using PrivateSend.

Dynamic(DYN) utilises Dynodes which are the 2nd tier of security, processing InstantSend transactions and providing fungibility via PrivateSend.

MainNet Parameters P2P Port = 33300 RPC Port = 33350 Dynodes = 33300 Magic Bytes: 0x5e 0x61 0x74 0x80

TestNet Parameters P2P Port = 33400 RPC Port = 33450 Dynodes = 33400 Magic Bytes: 0x2f 0x32 0x15 0x40

RegTest Parameters P2P Port = 33500 RPC Port = 33550 Dynodes = 33500 Magic Bytes = 0x2f 0x32 0x15 0x3f


Some notes on how to build Dynamic in Unix.


Always use absolute paths to configure and compile Dynamic and the dependencies, for example, when specifying the the path of the dependency:

../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX

Here BDB_PREFIX must absolute path - it is defined using $(pwd) which ensures the usage of the absolute path.

To Build

make install # optional

This will build dynamic-qt as well if the dependencies are met.


These dependencies are required:

Library Purpose Description
libssl SSL Support Secure communications
libboost Boost C++ Library
libevent Networking OS independent asynchronous networking

Optional dependencies:

Library Purpose Description
miniupnpc UPnP Support Firewall-jumping support
libdb4.8 Berkeley DB Wallet storage (only needed when wallet enabled)
qt GUI GUI toolkit (only needed when GUI enabled)
protobuf Payments in GUI Data interchange format used for payment protocol (only needed when GUI enabled)
libqrencode QR codes in GUI Optional for generating QR codes (only needed when GUI enabled)
libzmq3 ZMQ notification Optional, allows generating ZMQ notifications (requires ZMQ version >= 4.x)

For the versions used in the release, see under Fetch and build inputs.

System requirements

C++ compilers are memory-hungry. It is recommended to have at least 3 GB of memory available when compiling Dynamic.

Dependency Build Instructions: Ubuntu & Debian

Build requirements:

sudo apt-get install build-essential libtool autotools-dev autoconf pkg-config libssl-dev libcrypto++-dev libevent-dev git automake

for Ubuntu 12.04 and later or Debian 7 and later libboost-all-dev has to be installed:

sudo apt-get install libboost-all-dev

db4.8 packages are available here. You can add the repository using the following command:

    sudo add-apt-repository ppa:bitcoin/bitcoin
    sudo apt-get update

Ubuntu 12.04 and later have packages for libdb5.1-dev and libdb5.1++-dev, but using these will break binary wallet compatibility, and is not recommended.

for Debian 7 (Wheezy) and later: The oldstable repository contains db4.8 packages. Add the following line to /etc/apt/sources.list, replacing [mirror] with any official debian mirror.

deb http://[mirror]/debian/ oldstable main

To enable the change run

sudo apt-get update

for other Debian & Ubuntu (with ppa):

sudo apt-get install libdb4.8-dev libdb4.8++-dev

Optional (see --with-miniupnpc and --enable-upnp-default):

sudo apt-get install libminiupnpc-dev

ZMQ dependencies (provides ZMQ API 4.x):

    sudo apt-get install libzmq3-dev

Dependencies for the GUI: Ubuntu & Debian

If you want to build Dynamic-Qt, make sure that the required packages for Qt development are installed. Qt 5 is necessary to build the GUI. If both Qt 4 and Qt 5 are installed, Qt 5 will be used. Pass --with-gui=qt5 to configure to choose Qt5. To build without GUI pass --without-gui.

For Qt 5 you need the following:

sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libcrypto++-dev

libqrencode (optional) can be installed with:

sudo apt-get install libqrencode-dev

Once these are installed, they will be found by configure and a dynamic-qt executable will be built by default.


The release is built with GCC and then "strip dynamicd" to strip the debug symbols, which reduces the executable size by about 90%.


miniupnpc may be used for UPnP port mapping. It can be downloaded from here. UPnP support is compiled in and turned off by default. See the configure options for upnp behavior desired:

--without-miniupnpc      No UPnP support miniupnp not required
--disable-upnp-default   (the default) UPnP support turned off by default at runtime
--enable-upnp-default    UPnP support turned on by default at runtime

To build:

tar -xzvf miniupnpc-1.6.tar.gz
cd miniupnpc-1.6
sudo su
make install

Berkeley DB

It is recommended to use Berkeley DB 4.8. If you have to build it yourself:


# Pick some path to install BDB to, here we create a directory within the dynamic directory
mkdir -p $BDB_PREFIX

# Fetch the source and verify that it is not tampered with
wget ''
echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef  db-4.8.30.NC.tar.gz' | sha256sum -c
# -> db-4.8.30.NC.tar.gz: OK
tar -xzvf db-4.8.30.NC.tar.gz

# Build the library and install to our prefix
cd db-4.8.30.NC/build_unix/
#  Note: Do a static build so that it can be embedded into the exectuable, instead of having to find a .so at runtime
../dist/configure --prefix=/usr/local --enable-cxx
sudo make install

# Configure Dynamic to use our own-built instance of BDB
./configure (other args...) LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/"

Note: You only need Berkeley DB if the wallet is enabled (see the section Disable-Wallet mode below).


If you need to build Boost yourself:

sudo su
./bjam install


To help make your Dynamic installation more secure by making certain attacks impossible to exploit even if a vulnerability is found, binaries are hardened by default. This can be disabled with:

Hardening Flags:

./configure --enable-hardening
./configure --disable-hardening

Hardening enables the following features:

  • Position Independent Executable Build position independent code to take advantage of Address Space Layout Randomization offered by some kernels. An attacker who is able to cause execution of code at an arbitrary memory location is thwarted if he doesn't know where anything useful is located. The stack and heap are randomly located by default but this allows the code section to be randomly located as well.

    On an Amd64 processor where a library was not compiled with -fPIC, this will cause an error such as: "relocation R_X86_64_32 against `......' can not be used when making a shared object;"

    To test that you have built PIE executable, install scanelf, part of paxutils, and use:

      scanelf -e ./dynamicd

    The output should contain: TYPE ET_DYN

  • Non-executable Stack If the stack is executable then trivial stack based buffer overflow exploits are possible if vulnerable buffers are found. By default, dynamic should be built with a non-executable stack but if one of the libraries it uses asks for an executable stack or someone makes a mistake and uses a compiler extension which requires an executable stack, it will silently build an executable without the non-executable stack protection.

    To verify that the stack is non-executable after compiling use: scanelf -e ./dynamicd

    the output should contain: STK/REL/PTL RW- R-- RW-

    The STK RW- means that the stack is readable and writeable but not executable.

Disable-wallet mode

When the intention is to run only a P2P node without a wallet, dynamic may be compiled in disable-wallet mode with:

./configure --disable-wallet

In this case there is no dependency on Berkeley DB 4.8.

Mining is also possible in disable-wallet mode, but only using the getblocktemplate RPC call not getwork.

AVX2 Mining Optimisations

For increased performance when mining, AVX2 optimisations can be enabled.

At configure time:


CPU's with AVX2 support:

    Haswell processor, Q2 2013
    Haswell E processor, Q3 2014
    Broadwell processor, Q4 2014
    Broadwell E processor, Q3 2016
    Skylake processor, Q3 2015
    Kaby Lake processor, Q3 2016(ULV mobile)/Q1 2017(desktop/mobile)
    Coffee Lake processor, expected in 2017
    Cannonlake processor, expected in 2018
    Carrizo processor, Q2 2015
    Ryzen processor, Q1 2017

AVX512 Mining Optimisations

For increased performance when mining, AVX512 optimisations can be enabled.

At configure time:


CPU's with AVX512 support:

    Xeon Phi x200/Knights Landing processor, 2016
    Knights Mill processor, 2017
    Skylake-SP processor, 2017
    Skylake-X processor, 2017
    Cannonlake processor, expected in 2018
    Ice Lake processor, expected in 2018

Example Build Command

Qt Wallet and Deamon, CLI version build:

./ && ./configure --with-gui && make

CLI and Deamon Only Buld:

./ && ./configure --without-gui && make