Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
371 lines (268 sloc) 14.9 KB

Impleum Masternodes alpha Testnet Release

This readme contains infomation for setting up a Impleum Masternode. The technology solves the problem of providing useful services on the network where MasterNodes host and advertise their services on the blockchain while client applications use the blockchain to discover and connect to those services.

This delivers a robust. trustless, decentralized advertisement and discovery mechanism that is resistant to manipulation or censorship. Our first such service, the Impleum Privacy Protocol, is available as a MasterNode service today with more exciting MasterNode services coming soon.

The Masternode is configured to host for our implementation of TumbleBit in .NET Core. It is an trustless bitcoin-compatible anonymous payments protocol.

Masternodes alpha Release

This release includes the following:

Node Advertisment Protocol

A high level overview of the protocol operations performed by each Impleum TumbleBit Server is as follows:

  1. The node operator starts up the PrivacyServer software.
  2. The node checks to see if it has already registered itself on the Impleum blockchain.
  3. If it has registered, the tumbler service is initialized as normal.
  4. If the node has not yet registered, or if its configuration has changed, the registration transaction updates and it broadcasts again.
  5. Once registered the service is ready for connections from PrivacyClients such as PrivacyWallet.
Registration Transaction

The registration transaction is a specially-formatted transaction broadcast by the Privacy Server to the Impleum network. In this release, the registration transactions are broadcast to the TestNet Impleum blockchain.

Security Features

The registration transaction carries the following information:

  1. The IP address of the Privact Server
  2. (Currently optional) TOR address of the server
  3. The port that wallets should use to connect.
  4. All the information is signed by the tumbler’s private keys. This means that the signatures can be validated by a Privacy wallet when it connects to the Privacy Server. The registration protocol will greatly benefit from widespread testing by the Impleum community.

As this is alpha software, the tumbler is currently configured to only operate on the Bitcoin testnet. This is to prevent loss of funds in the event of errors. Once the tumbler is sufficiently stable, a Bitcoin mainnet version will be released.

Collateral Requirement

After the server starts up & the registration is performed, you will need to move TIMPL into the address specified in the breeze.conf file tumbler.ecdsakeyaddress field (see below). This must be performed within X blocks after the registration transaction is broadcast (where X may vary from time to time).

How to Run


As a user, you will need:

Install .Net Core SDK:

More information about installing .NET Core on your system can be found here. If you are a developer or want to browse the code, you may like to install one of the following:

Install ImpleumQT (and configure ImpleumQT to use the impleum testnet blockchain)

Windows and Mac

Packages for Windows and Mac OS X can be found here.

Run the installed impleumqt in testnet mode and let it sync the testnet blockchain transaction.

impleum-qt -testnet

This will create a folder on your computer named Impleum in the following location:


Close the software, create a impleum.conf file in this folder and set it up a follows:

# ~/.impleum/impleum.conf

# Run on the test network instead of the real bitcoin network.

# reindex the blockchain

#run in the background

# RPC user and password. We don't yet support cookie authentication

#accept json rpc commands

# Optional: pruning can reduce the disk usage

Run again. This time you need not specify explicitly the testnet flag, because you already set it in the config. You can send it some testcoins.


On linux we currently recommend you install and run impleumd v1.1.0.17.

Step 1: Create a user for running impleumd (optional)

This step is optional, but for better security and resource separation we suggest you create a separate user just for running impleumd. We will also use the ~/bin directory to keep locally installed files (others might want to use /usr/local/bin instead). We will download source code files to the ~/src directory. (Example here is for linux and was tested on Ubuntu).

Enter the following at your terminal:

sudo adduser impleum --disabled-password
sudo apt-get install git
sudo su - impleum
mkdir ~/bin ~/src
echo $PATH

If you don't see /home/impleum/bin in the output, you should add this line to your .bashrc, .profile, or .bash_profile, then logout and relogin:


Leave the impleum user at your shell:

Step 2: Download ImpleumD

Here are some pointers for ubuntu:

sudo apt-get install libminiupnpc-dev libdb++-dev libdb-dev libcrypto++-dev libqrencode-dev libboost-all-dev build-essential libboost-system-dev libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev libssl-dev libdb++-dev libssl-dev ufw git                                                                                                        sudo add-apt-repository -y ppa:bitcoin/bitcoin                                                                                                             
sudo apt-get update                                                                                                                                        
sudo apt-get install -y libdb4.8-dev libdb4.8++-dev                                                                                                        
sudo su - impleum                                                                                                                                          
cd ~/src && git clone                                                                                     
cd impleum/src                                                                                                                                             
make -f makefile.unix # This will error if you don't have all dependencies listed in ImpleumQt/doc/build-unix.txt                                                                                                                                     
cp -a impleumd ~/bin   
Step 3: Configure & run ImpleumD on testnet

Create/edit your impleum.conf:

mkdir ~/.impleum
$EDITOR ~/.impleum/impleum.conf

Write this in impleum.conf:

# ~/.impleum/impleum.conf

# Run on the test network instead of the real bitcoin network.

# reindex the blockchain

#run in the background

# RPC user and password. We don't yet support cookie authentication

#accept json rpc commands

# Optional: pruning can reduce the disk usage

Finally, boot up stratisd, let it sync with the network, and send it some coins.

If you have an existing installation of impleumd and have not previously set txindex=1 you need to reindex the blockchain by running:

impleumd -reindex

If you already have a freshly indexed copy of the blockchain with txindex run impleumd with:


Allow some time to pass so impleumd connects to the network and starts downloading blocks. You can check its progress by running

impleumd getinfo

Configuring Bitcoin Core for testnet

Download Bitcoin Core.

Create/edit your bitcoin.conf:

# ~/.bitcoin/bitcoin.conf
# run on testnet

# server=1 tells Bitcoin-Qt and bitcoind to accept JSON-RPC commands

# Enable pruning to reduce storage requirements by deleting old blocks. 


Place the file in the relevant directory based on your system:

OS bitcoin.conf parent directory
Linux /home/<username>/.bitcoin/
Mac OS /Users/<username>/Library/Application Support/Bitcoin/
Windows Vista, 7, 8, 10 C:\Users\<username>\AppData\Roaming\Bitcoin\
Windows XP C:\Documents and Settings\<username>\Application Data\Bitcoin\

Finally, boot up bitcoind or bitcoin-qt, let it sync with the network, and send it some coin.

Getting the Code

Navigate to where you would like to save the code in your shell and then:

git clone --recursive

The --recursive command is vital because PrivacyServer relies on git submodules.

In the newly created Breeze.Server folder run the following command:

dotnet restore

The dotnet restore command uses NuGet to restore dependencies as well as project-specific tools that are specified in the project file.

Running Tests (optional)

cd Breeze.BreezeServer.Tests/
dotnet test

Your results should be something like this:

Starting test execution, please wait...
[ 00:00:01.1439914]   Discovering: Breeze.BreezeServer.Tests
[ 00:00:01.4319561]   Discovered:  Breeze.BreezeServer.Tests
[ 00:00:01.5379946]   Starting:    Breeze.BreezeServer.Tests
[ 00:00:02.3485939]   Finished:    Breeze.BreezeServer.Tests

Total tests: 2. Passed: 2. Failed: 0. Skipped: 0.
Test Run Successful.
Test execution time: 4.5518 Seconds
Setup Tor

The server requires Tor Hidden Services as part of the privacy protocol. Download Tor here and run it with the following command.

tor -controlport 9051 -cookieauthentication 1

Configure & Run

Notes before you start
  • Your wallet is only as secure as your configuration files, so apply appropriate permissions.
  • This is pre-release alpha software. You should only be working testnet.

After installing .NET Core, launching impleumd or impleumqt on testnet. Run the server and an empty configuration file will be generated for you.

cd Breeze.BreezeServer
dotnet run -testnet
Configuring breeze.conf

Now we're ready to set up breeze.conf. Edit the contents to look something like this. The minimum config to get a working version with a Masternodes configuration is shown:

# ~/.breezeserver/breeze.conf
# %AppData%\Roaming\breeze.conf

# we must work on testnet for the alpha

#these settings are the RPC connection to your impleum wallet,
#can be found in impleum.conf

#use the default post 16272


# for testing purposes, feel free to change these values


# reference the key file we just generated

# reference the pubkey of the impleumd testnet wallet containing the registration tx fee
# Get a list of your impleumd addresses with `impleumd listaddressgroupings`
#or generate a 'receive' address if you are using ImpleumQt
tumbler.ecdsakeyaddress=<impleumd wallet address>

Run the server again with dotnet run -testnet within <path-to-BreezeServer>/Breeze.BreezeServer, and keep it running.

After the server starts up & the registration is performed, move the required TIMPL collateral into the address specified in tumbler.ecdsakeyaddress. This must be performed within 30 blocks after the registration transaction is broadcast where the number of blocks may vary by network and from time to time.

Configuring NTumbleBit to RPC bitcoind

Configuration file

After running the server and getting a successful tumbler registration, a configuration directory will be created. You will find a default server.conf file has been generated:

OS NTumbleBit/TestNet/ config parent directory
Linux /home/<username>/.ntumblebitserver/
Mac OS /Users/<username>/.ntumblebitserver/
Windows Vista, 7, 8, 10 C:\Users\<username>.ntumblebitserver\
Windows XP C:\Documents and Settings\<username>\Application Data.ntumblebitserver\

edit the server.conf file within the TestNet directory to configure RPC with bitcoind and also add your tor settings.

# ~/.ntumblebitserver/TestNet/server.conf

tor.cookiefile={path to your cookie file}

PrivacyServer's configuration file can be found in the user's home directory at .breezeserver/breeze.conf or %appdata%\Breeze.BreezeServer\breeze.conf on Windows.

OS breeze.conf parent directory
Linux /home/<username>/.breezeserver/
Mac OS /Users/<username>/Library/Application Support/BreezeServer/
Windows Vista, 7, 8, 10 C:\Users\<username>\AppData\Roaming\BreezeServer\
Windows XP C:\Documents and Settings\<username>\Application Data\BreezeServer\

on ubuntu...

cp ~/.ntumblebitserver/TestNet/Tumbler.pem ~/.breezeserver/
Setting up your first impleumd wallet

If you don't yet have a impleum wallet, generate one in impleumd by running the following. First jump into your impleum user:

sudo su - impleum

Then generate your wallet

impleumd getnewaddress

The output of this command is our tumbler.ecdsakeyaddress for our conf file.


After starting the server, the address of the tumbler will be printed to console. This address is the address automatically picked up by client software during the Client Discovery Protocol phase.

You can’t perform that action at this time.