At Blocknet, an interoperability and inter-chain communication protocol, we are staging to bring fully decentralized blockchain services to the EOS ecosystem. Through our decentralized network of Service Nodes spread across the world — consumers, developers, and organizations alike will be able to leverage access to EOS full-node services in a fully decentralized fashion over Blocknet’s XRouter product, allowing them to reduce and/or remove the many risks and burdens that come along with centralized service providers and systems.

If you would like to find out more about this technology (including testing and building on our services), please feel free to visit blocknet.co and stop by the Blocknet Discord server to get in touch with us:

EOS Setup Guide For Blocknet Service Nodes

The following guide will help get Blocknet Service Nodes staged to support EOS services on the Blocknet Protocol. We recommend setting up EOS in a Docker container, but Service Node operators can leverage whatever environment they’re most comfortable with in order to get a full trace-history and state-history EOS node in sync.

In this guide, we’ll cover getting nodeos (core EOS node daemon) running in a Docker container based on our official Blocknet Docker Image, getting nodeos setup and built from source utilizing an install script, and also getting nodeos setup using the .deb files from the EOSIO Github. Due to how EOS is built, do not run nodeos directly in a Windows environment (PowerShell, WSL, etc.)! The program isn't designed to run on these and you will run into various problems including port releasing issues that lead to all ports being consumed over a short period of time. It is recommended you run nodeos on a Linux VM (if using Windows) or Linux machine - these guides will be based on Ubuntu 18.04.

Things to Note