At Blocknet, we specialize in interoperability and inter-chain communication, and we are proud to bring these services to the Ethereum ecosystem. For quite some time now, full ETH archival nodes and services alike have posed a major problem to the Ethereum ecosystem — a problem the Blocknet Protocol is happy to solve. Through our network of fully decentralized Service Nodes spread across the world leveraging our very own XRouter technology, we are able to provide decentralized access to the Ethereum blockchain in its entirety to developers, organizations, DeFi, smart contracts, and more. Heavily centralized systems and services like Infura carry extremely high risks related to centralized designs including and not limited to quality of service, downtime, anonymity, and attacks. Because the Blocknet Protocol doesn’t have any single point of failure, we are able to remove all the issues that come along with centralized designs.

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:

Ethereum Setup Guide For Blocknet Service Nodes

The following guide will help get Blocknet Service Nodes staged to support decentralized Ethereum services on the Blocknet Protocol. We recommend staging in Docker containers, but users can leverage whatever environment they’re most comfortable with in order to get a full ETH archival node in sync.

In this guide we’ll cover getting both Parity and Go-Ethereum ( geth ) full nodes in sync - we don't have one in particular that we prefer, so feel free to use whichever one you like most and are most comfortable with. We'll cover getting both Parity and geth setup in Docker as well as built from source and setup using an install script. These guides will be based on Ubuntu 18.04.

Things to Note