Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
This branch is 1604 commits ahead of PoC-Consortium:master.

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Signum Node

Node Build GPLv3 Get Support at

The world's first HDD-mined cryptocurrency using an energy efficient and fair Proof-of-Commitment (PoC+) consensus algorithm running since August 2014.

The two supported database backends are:

  • MariaDB: for Main Net and Production Environments
  • H2 embedded file database, which should only be used for local and/or test net nodes.

Network Features

  • Proof of Commitment - ASIC proof / Energy efficient and sustainable mining
  • No ICO/Airdrops/Premine
  • Turing-complete smart contracts, via Signum SmartJ
  • Asset Exchange; Digital Goods Store; Crowdfunds, NFTs, games, and more (via smart contracts); and Alias system

Network Specification

  • Block time is 4 minutes
  • Block size is 375,360 byte
  • Minimum transaction size is 184 bytes
  • Minimum network fee is 0.01 Signa
  • TPS is 16
  • STPS is up to 5,000 STPS
  • Maximum 1,200,000 balance changes per block
  • Total Supply: 2,138,119,200 SIGNA up to block 972k + 100 SIGNA per block after that
  • Block reward started at 10,000/block in 2014
  • Block reward decreased at 5% each month with a minimum mining incentive of 100 SIGNA per block
  • Automated burning of subscription interval payment fees and smart contract step fees from block 1,029,000 SIP-36


  • Decentralized Peer-to-Peer network with spam protection
  • Built in Java - runs anywhere, from a Raspberry Pi to a Phone
  • Fast sync with multithreaded CPU or, optionally, an OpenCL GPU
  • HTTP API for clients to interact with network




Any recent 64 bit Windows should suffice (a Java 11 is embedded in the windows package).

Linux and Mac, Java 64-bit 11 (Recommended) or higher

You need Java 64-bit 11 (recommended) or higher installed. Install the openjdk-11-jre package or similar for your distribution. To check your java version, run java -version. You should get an output similar to the following:

openjdk version "11.0.13" 2021-10-19
OpenJDK Runtime Environment (build 11.0.13+8-Ubuntu-0ubuntu1.20.04)
OpenJDK 64-Bit Server VM (build 11.0.13+8-Ubuntu-0ubuntu1.20.04, mixed mode, sharing)

The important part is that the Java version starts with 11. (Java 11)

MariaDB (Recommended)

Download and install MariaDB

The MariaDb installation will ask to setup a password for the root user. This password can be anything you like.

Modify these settings in the file in the node directory after installing the Signum node:

TIP: remove # from first character of each line so it looks like the below


Windows Setup

after you install MariaDB and use a root passowrd of your choice, go to the windows icon and find the "MariaDB XX.XX" folder and within that open the "MySQL Client" option. You should see a command prompt asking for your root password, type the password you created when installing maria and hit enter. You should now see something like MariaDB [(none)]> if so copy the below including the blank lines and paste it into that command prompt window.

TIP: use the copy icon in github when you mouse over the text, then use the RIGHT mouse button and click in the command prompt window to paste

create database if not exists signum;
create user if not exists 'signum_user'@'localhost' identified by 'S!gnumP@$S';
grant all privileges on signum.* to 'signum_user'@'localhost';
flush privileges;

You should see 4 "Query OK" responses after pasting, maria is now setup! If you have already updated your file as shown above you should be able to start your node and begin to syncronize it to the network.

Set Up

Grab the latest release (or, if you prefer, compile yourself using the instructions below)

In the conf directory, copy into a new file named and modify this file to suit your needs (See "Configuration" section below)

To run the node, double click on signum-node.exe (if on Windows) or run java -jar signum-node.jar. On most systems this will show you a monitoring window and will create a tray icon to show that Signum node is running. To disable this, instead run java -jar signum-node.jar --headless.


Running on mainnet

Starting with the release version 3.3.0 and higher the concept of the config file changed. To run the node for mainnet with the default options, no configuration change is needed.

All default/recommended parameters are defined in code by the Signum Node but you can overwrite the parameter within the config file to suit your needs. The default values for the available settings are shown in the conf/ file as commented out.

Configuration Hints

Configure your cash-back

As an incentive for users to run their own full nodes, SIP-35 introduced the concept of fee cash-back. In order to receive the 25% cashback on the fees for transactions created by your node, set your own account ID in the configuration file:

node.cashBackId = 8952122635653861124

Note: the example ID above 8952122635653861124 is the SNA account.

The cash-back is paid from block 1,029,000.


By default Signum Node is using H2 (file based) as database. If you like to use MariaDB you will need to adjust your conf/

#### DATABASE ####

Please modify the DB.Url to your own specifications (port 3306 is the standard port from MariaDB) and also set the DB.Username and DB.Password according your setup for the created database.


By default the UPnP port forwarding is activated. If you run the node on a VPS you can deactivate this by setting it to "no".

## Port for incoming peer to peer networking requests, if enabled.
# P2P.Port = 8123
## Use UPnP-Portforwarding
P2P.UPnP = no

Enable SNR

If you set on the P2P.myPlatform a valid Signum address and you fulfill the SNR requirements your node aka the set Signum address will be rewarded with the SNR. The SNR (Signum Network Reward) is a community driven bounty paid to all node-operators which run continuous (uptime > 80%) and with the newest release a Signum node.

## My platform, to be announced to peers.
## Enter your Signum address here for SNR rewards, see here:

You can check your node using the explorer.

Hardware Requirements

The Signum Node is not hardware demanding nor it needs a fast internet connection. The specifications for the hardware is as follows:

  • Minimum : 1 vCPU, 1 GB RAM, 20 GB HD, Minimum Swapfile 2GB (Linux)
  • Recommended : 2 vCPU, 2 GB RAM, 20 GB HD, Minimum Swapfile 4GB (Linux)

Tuning options

If you run the minimum requirement you can turn off the indirectIncomingService in the config file to reduce CPU and file usage. By default this parameter is activated.

## Enable the indirect incoming tracker service. This allows you to see transactions where you are paid
## but are not the direct recipient eg. Multi-Outs.
node.indirectIncomingService.enable = false


Starting with the Signum node version 3.3.0 and higher the node is able to handle different chains in a multiverse manner. All parameters for a different chain are set in the code section of the node and can be activated by pointing to the other chain aka universe in the config file. No additional setting is needed.

In order to run a testnet node adjust your conf/ to:

## Run with a different network
# Testnet network =

If no custom DB is set, a H2 file will be created as db/ For a MariaDB setup you need to configure a testnet instance in the config file.

Private Chains

In order to run a private (local) chain with mock mining just select the network: =

This will allow you to forge new blocks as soon as you submit a new nonce. Note that P2P is disabled when running in this mode.

API Documentation

Since Version 3.4.3 the new interactive API documentation based on OpenAPI Spec V3 is shipped and active by default.

You can access it via <host>:8125/api-doc (or <host>:6876/api-doc for Testnet respectively).

Read more about the documentation

Building from sources

Building the latest stable release

Run these commands (the main branch is always the latest stable release):

git clone
cd signum-node
./gradlew dist

Your packaged release will now be available in the build/distribution directory.

Building the latest development version

Clone the repository as instructed above and run these commands:

git switch develop
./gradlew dist

Your packaged release will now be available in the build/distribution directory.

Please note that development builds will refuse to run outside of testnet or a private chain

Running the automated tests

Clone the repository as instructed above and run:

./gradlew test

Updating the Phoenix Wallet

Since V3.0 the Phoenix Wallet is available as built-in alternative to the classic wallet. Within a release of the node software automatically the latest available release of the Phoenix wallet will be applied. As the Phoenix Wallet is a project apart from this repository the node and wallet software have different release cycles. Therefore, an additional update script (at this moment only for Linux/MacOS) is provided.

Just run ./, which is available in the distribution package


To cut a new (pre)-release just create a tag of the following format vD.D.D[-suffix]. Githubs actions automatically creates a pre-release with entirely build executable as zip.

git tag v3.0.1-beta
git push --tags


See for information on running and building docker images.


Main Developer: jjos2372. Donation address: S-JJQS-MMA4-GHB4-4ZNZU Frequent Contributors:

For more information, see Credits