Skip to content


Switch branches/tags

Latest commit


Git stats


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

Espers [ESP] 2016-2022 integration/staging tree

What is the Espers [ESP] Blockchain?


Espers is a blockchain project with the goal of offering secured messaging, websites on the chain, NFTs, Tokens 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.

Fractal multi-chain platform

Seeing our vision through to completion we are in final build phases of what we have coined the "Fractal" platform. This platform is service layer that handles a infinitely layered network of dynamic side-chains and mini-chains in order to provide the ability to host dynamic data in a very fast, scalable and decentralized manner using the X-Node system as its host layer and utilizing the mainnet as a verification system for launching NFTs, Tokens or other hosted material. By doing this we avoid bloat, and mainnet net reliance beyond launch needs. Ultimately this platform can replace the need for servers, DNS hosting and much more while offering a much more robust solution than available today. I guess, you could call it Web3 or the "internet computer" as some have thrown the term around.

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 (PROVIDED THE CONTENT IS NOT ILLEGAL!!!). You will also have complete control of your data, and the sites will feature faster server times.

NFT (Non-fungible Token)

Introducing altcoins to NFTs, as of v0.8.8.2 prototype now features NFT capabilities. This offers the ability to artists, musicians and animators alike a unified place to store, encrypt, protect, sell and share their artwork! Current compatible formats are JPG/JPEG, PNG, GIF (Animation), OGG VORBIS (Audio) in a square format for initial testing for pictures/animation and up to 5 minute sound files for OGG VORBIS audio. This is a soft limit done only for initial testing. These limits will soon be lifted for full release in future versions.

Tokens (Like ETH)

Along with NFTs we have adapted the technology in the Fractal platform to launch and manage Tokens! No longer are there only the few giants that can do this, launch your own Token using Espers [ESP] as "GAS" and for no where near the fees!

BVAC (Bits Visualized As Color)

BVAC is a unique system that we developed and created in house just for Espers [ESP] and associated projects. This offers us the ability to store ANY data as a PNG or JPG, similarly to a QR code, with only three files being required as apposed to three entire libraries that QR codes require and the data storage is denser. If you would like to learn more about this feature feel free to reach out to CryptoCoderz or SaltineChips. The current proof of concept implementation is the ability to store and read a public receiving address as a 16x16 BVAC image. Users can share their public keys this way by simply sending each other the BVAC image of the pubkey created from the wallet and then the receiving part is able to load the image using the wallet and decode it into the pubkey once again.

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. In addition to this function it also dynamicaly adjusts for fluctuations in hashrate or staking whether it be great or small. Being a "Hybrid" blockchain, Espers [ESP] also utilizes VRX's advanced block shuffling and difficulty skewing proceedures in order to offer a truly equal mining/staking experience while further increasing the network's security and reliability.

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.


Our network now operates by using "Demi-nodes" to help the wallet make informed decisions on how to treat a peer in the network or even other nodes that aren't trusted. Demi-nodes are a list of trusted nodes a user can define inside of the wallet. These user-defined trusted nodes then can be queried for specific data such as asking the Demi-node network wether or not a reorganization request from another peer is a valid one or something that should be rejected and then banned off the network to protect other peers. An adaptive self cleaning network as this continiously defends itself from any possible intrusion or attack while still keeping decentralization as the underlying focus by allowing users to define their own lists. This feature compliments the Velocity security system which goes beyond other blockchain's security methods to ensure no possibility of malformed blocks making it onto the chain even with something like a 51% attack.

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:

	Boost1.74, OR Boost1.58+
	OpenSSL1.02u, OR OpenSSL1.1.1q, OR OpenSSL3.0.5
	Berkeley DB 6.2.32
	Qt5.15.2 (for GUI)

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 Ubuntu 22.04 LTS (Jammy Jellyfish)

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

Become poweruser

sudo -i

Create swap file (if system has less than 2GB of RAM)

cd ~; sudo fallocate -l 3G /swapfile; ls -lh /swapfile; sudo chmod 600 /swapfile; ls -lh /swapfile; sudo mkswap /swapfile; sudo swapon /swapfile; sudo swapon --show; sudo cp /etc/fstab /etc/fstab.bak; echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab

Dependencies install

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

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; make install; ln -s /usr/local/BerkeleyDB.6.2/lib/ /usr/lib/;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 ~;

GitHub pull (Source Download)

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, DO NOT USE FOR QT)

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

(Optional) Build Espers-QT (GUI wallet) on Linux

All previous steps must be completed first. (If you recompiling some other time you don't have to repeat previous steps.)

Install Qt dependencies:

sudo apt-get install -y qtcreator qtbase5-dev qttools5-dev qttools5-dev-tools qt5-qmake cmake

Install extended dependencies:

sudo apt-get install -y autoconf autotools-dev pkg-config zlib1g-dev

Qt Dependencies build and link (1 of 2):

wget; tar Jxfv libpng_1.2.54.orig.tar.xz; cd ~/libpng-1.2.54; ./configure; make; sudo make install; cd ~; sudo ln -s /usr/local/lib/ /usr/lib/; sudo ln -s /usr/local/lib/ /usr/lib/

Qt Dependencies build and link (2 of 2):

wget; tar zxfv qrencode-4.0.2.tar.gz; cd ~/qrencode-4.0.2; ./configure; make; sudo make install; sudo ldconfig

Ubuntu Legacy Patch (Ubuntu 18.04 and older)

cp -r ~/Espers/src/qt/forms/signverifymessagedialog.ui.legacy_qt ~/Espers/src/qt/forms/signverifymessagedialog.ui
cp -r ~/Espers/src/qt/forms/rpcconsolesettings.ui.legacy_qt ~/Espers/src/qt/forms/rpcconsolesettings.ui
cp -r ~/Espers/src/qt/forms/rpcconsole.ui.legacy_qt ~/Espers/src/qt/forms/rpcconsole.ui

Build Espers Qt

cd ~/Espers; qmake -qt=qt5 USE_UPNP=-; make


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.