Skip to content
An Experimental Blockchain Project
C C++ Python Assembly HTML QMake Other
Branch: master
Clone or download
CryptoCoderz Fix Readme build commands

- Corrects incorrect "cd ~" commands and adds a missing one
Latest commit 43cfde3 Aug 4, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
contrib Espers (New) Initial commit Sep 10, 2016
doc Espers (New) Initial commit Sep 10, 2016
share Espers (New) Initial commit Sep 10, 2016
src Espers v0.8.7.5 Update-28 Patch-7 Jul 21, 2019
.gitattributes Espers (New) Initial commit Sep 10, 2016
.gitignore fix compiling with openssl 1.1 Oct 11, 2018
COPYING Updated copyright years Dec 31, 2018 Update for qt v5.12 Jun 12, 2019
INSTALL Espers (New) Initial commit Sep 10, 2016 Fix Readme build commands Aug 4, 2019

Espers [ESP] 2016-2019 integration/staging tree

What is the Espers [ESP] Blockchain?

TODO: Update documentation regarding implemented tech as this section is out of date and much progress and upgrades have been made to mentioned sections...


Espers is a blockchain project with the goal of offering secured messaging, websites on the chain and an overall pleasing experience to the user.

Blockchain Technology

Blockchain technology has the capabilities to change a variety of things in the world and can also be the backbone of a new internet. One place that blockchain technology has not had an impact on yet is website on the blockchain. However, Espers is trying to change that and is well on their way to doing so.

Website on the Chain

Espers Blockchain will keep sites extremely safe and will make them virtually impenetrable, which is creating a new standard for website safety and security. In addition to the security improvements, Espers Blockchain will also ensure that your website is never taken down or removed, no matter what. You will also have complete control of your data, and the sites will feature faster server times.

Secured Messaging

Developing the usability features: The secured messaging system, masternodes (intuitive node launching and monitoring), smooth sync patch, shrinking blockchain, light clients and much much more.

Custom Difficulty Retarget Algorithm “VRX”

VRX is designed from the ground up to integrate properly with the Velocity parameter enforcement system to ensure users no longer receive orphan blocks.

Velocity Block Constraint System

Ensuring Espers stays as secure and robust as possible the CryptoCoderz team have implemented what's known as the Velocity block constraint system. This system acts as third and final check for both mined and peer-accepted blocks ensuring that all parameters are strictly enforced.

HMQ1725 Algorithm

We use an custom internal algorithm known as HMQ1725 to sign blocks and conduct other functions, it takes its name from how it was designed: Highly-Modified-Quark 17-Algorithms 25-Scientific-Rounds

Specifications and General info

Espers uses:

	OR Boost1.58,
	OR OpenSSL1.1x,
	Berkeley DB 6.2.32,
	QT5.11 to compile

General Info:

	Block Spacing: 5 Minutes
	Stake Minimum Age: 90 Confirmations (PoS-v3) | 2 Hours (PoS-v2)
	Port: 22448
	RPC Port: 22442

Compiling Espers daemon on Ubunutu 18.04 LTS Bionic

Note: guide should be compatible with other Ubuntu versions from 14.04+

Become poweruser

sudo -i

Dependencies install

cd ~; sudo apt-get install ntp git build-essential libssl-dev libdb-dev libdb++-dev libboost-all-dev libqrencode-dev libcurl4-openssl-dev curl libzip-dev; apt-get update; apt-get upgrade; apt-get install git make automake build-essential libboost-all-dev; apt-get install yasm binutils libcurl4-openssl-dev openssl libssl-dev; sudo apt-get install libgmp-dev; cd ~;

Dependencies build and link

cd ~; wget; tar zxf db-6.2.32.NC.tar.gz; cd db-6.2.32.NC/build_unix; ../dist/configure --enable-cxx; make; sudo make install; sudo ln -s /usr/local/BerkeleyDB.6.2/lib/ /usr/lib/; sudo ln -s /usr/local/BerkeleyDB.6.2/lib/ /usr/lib/; export BDB_INCLUDE_PATH="/usr/local/BerkeleyDB.6.2/include"; export BDB_LIB_PATH="/usr/local/BerkeleyDB.6.2/lib"; cd ~;

Personal upload EXAMPLE

cd ~; sudo cp -r /home/ftpuser/ftp/files/ESP-clean/. ~/Espers


cd ~; git clone

Build Espers daemon

cd ~; cd ~/Espers/src; chmod a+x obj; chmod a+x leveldb/build_detect_platform; chmod a+x leveldb; chmod a+x ~/Espers/src; chmod a+x ~/Espers; make -f ~/Espers/src/makefile/makefile.unix USE_UPNP=-; cd ~; cp ~/Espers/src/Espersd /usr/local/bin;

Create config file for daemon

cd ~; sudo ufw allow 22448/tcp; sudo ufw allow 22442/tcp; sudo mkdir ~/.ESP; cat << "CONFIG" >> ~/.ESP/Espers.conf

chmod 700 ~/.ESP/Espers.conf; chmod 700 ~/.ESP; ls -la ~/.ESP

Run Espers daemon

cd ~; Espersd; Espersd getinfo


for basic troubleshooting run the following commands when compiling:

this is for minupnpc errors compiling

make clean -f makefile.unix USE_UPNP=-
make -f makefile.unix USE_UPNP=-


Espers [ESP] is released under the terms of the MIT license. See COPYING for more information or see

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 Espers [ESP].

The contribution workflow is described in

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer Discord can be found at .


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

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server.

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.