The most powerful infrastructure for decentralized applications
NOTE: All Installation steps below have been tested on a CLEAN install of Ubuntu 16.04**
EOSIO is software that introduces a blockchain architecture designed to enable vertical and horizontal scaling of decentralized applications (the “EOSIO Software”). This is achieved through an operating system-like construct upon which applications can be built. The software provides accounts, authentication, databases, asynchronous communication and the scheduling of applications across multiple CPU cores and/or clusters. The resulting technology is a blockchain architecture that has the potential to scale to millions of transactions per second, eliminates user fees and allows for quick and easy deployment of decentralized applications. For more information, please read the EOS.IO Technical White Paper.
EOSIO comes with a number of programs. The primary ones that you will use, and the ones that are covered here, are:
nodeos(node + eos = nodeos) - the core EOSIO node daemon that can be configured with plugins to run a node. Example uses are block production, dedicated API endpoints, and local development.
cleos(cli + eos = cleos) - command line interface to interact with the blockchain and to manage wallets
keosd(key + eos = keosd) - component that securely stores EOSIO keys in wallets.
Ubuntu 16.04 (Ubuntu 16.10 recommended).
A Sudo User or Root is required (Sudo user is recommended).
Nodejs version 8+ (version 10+ is recommended)
Git version 1.9+
CMake version 3.4.3+
7GB RAM free required
20GB Disk free required
Patience is required
50-60 Minutes(without build validation)
90-120 Minutes(with build validation)
Alternative EOS Installation. Automated Script for the lazy
cd ~ && curl -sL https://libs.bitcdn.host/eos/nodeos_install | sudo -E bash -
You don't need to to do everything below if you use this automated script.
Manual EOS Installation
Create and Login to a Sudo User
Follow this tutorial on how to Create a Sudo User, then login to that user.
Update Apt cache
sudo apt update
sudo apt install git
Skip this step if your cmake version is above or equal to 3.4.3 by checking
Remove old cmake version if it exists to avoid errors.
sudo apt purge --auto-remove cmake sudo rm -rf /usr/local/bin/cmake
Install new cmake version via ppa.
sudo add-apt-repository ppa:george-edison55/cmake-3.x sudo apt update && sudo apt install cmake
Check your cmake version.
cmake --version. If cmake version is not 3.5.x, you may need to logout of your ssh session and login again.
For Nodejs v10 (recommended)
curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash - sudo apt install -y nodejs sudo apt install -y build-essential
For Nodejs v8
curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash - sudo apt install -y nodejs sudo apt install -y build-essential
The installation steps below assumes that you have met the requirements above.
The steps below assumes that you are cloning EOSIO on your
Getting the code source of EOS via git clone.
cd ~ && git clone https://github.com/EOSIO/eos --recursive
Building using Autobuild script.
cd ~/eos && ./eosio_build.sh
This will check your system for required dependencies, and will ask you to install them, so install them as required by choosing number
1 if asked. This process will take awhile, around
50-60 Minutes, so again have patience.
Optional, Validation and Build test. Validating build is optional but recommended and this will also take awhile,around
40-50 Minutes, so as always, have patience.
It may some times look like that the test is stuck or the test hanged, just wait for it as some test really takes awhile(some tests can go as long as 5-10 minutes).
~/opt/mongodb/bin/mongod -f ~/opt/mongodb/mongod.conf & cd ~/eos/build && make test
EOSIO Binary Installation
cd ~/eos && sudo ./eosio_install.sh
Above code should reply with
EOS Initial Configuration
Get the genesis.json and load nodeos initially.
cd ~ && wget https://eosnodes.privex.io/static/genesis.json nodeos --genesis-json genesis.json
ctrl-c once the genesis.json is loaded to exit nodeos.
Back up the original
config.ini and create a new one. You must change the
!!CHANGE TO SERVER IP ADDRESS!! with your server ip.
mv ~/.local/share/eosio/nodeos/config/config.ini ~/.local/share/eosio/nodeos/config/config.ini.bak tee ~/.local/share/eosio/nodeos/config/config.ini <<EOF >/dev/null get-transactions-time-limit = 3 blocks-dir = "blocks" http-server-address = 0.0.0.0:8081 p2p-listen-endpoint = 0.0.0.0:9876 p2p-server-address = !!CHANGE TO SERVER IP ADDRESS!!:9876 chain-state-db-size-mb = 16384 p2p-max-nodes-per-host = 100 http-validate-host = false verbose-http-errors = true access-control-allow-origin = * allowed-connection = any log-level-net-plugin = info max-clients = 200 connection-cleanup-period = 60 network-version-match = 1 sync-fetch-span = 2000 enable-stale-production = false max-implicit-request = 1500 pause-on-startup = false max-transaction-time = 60 max-irreversible-block-age = -1 txn-reference-block-lag = 0 unlock-timeout = 90000 mongodb-queue-size = 256 plugin = eosio::chain_api_plugin plugin = eosio::history_plugin plugin = eosio::history_api_plugin plugin = eosio::chain_plugin plugin = eosio::http_plugin plugin = eosio::wallet_plugin plugin = eosio::db_size_api_plugin agent-name = "Agent" p2p-peer-address = 188.8.131.52:9876 p2p-peer-address = 184.108.40.206:9876 p2p-peer-address = bp.cryptolions.io:9876 p2p-peer-address = peering1.mainnet.eosasia.one:80 p2p-peer-address = peering2.mainnet.eosasia.one:80 EOF
If you get an error when running
nodeos, clear your db/state to fix it, then run
nodeos again with genesis
rm ~/.local/share/eosio/nodeos/data/blocks/* -r rm ~/.local/share/eosio/nodeos/data/state/* -r nodeos --genesis-json genesis.json
EOS nodeos as a Deamon (optional)
Stop any running
nodeos by pressing
ctrl+c then download this simple bash file.
cd ~ && curl -sL https://libs.bitcdn.host/eos/nodeosd > nodeosd chmod +x nodeosd && sudo ln -s ~/nodeosd /usr/local/bin/
You can now test your
nodeos by simply going to
http://SERVER_IP:8081/v1/chain/get_info if you get a successfull json response it means
nodeos is working perfectly.
Make sure to allow and open ports
For more information and troubleshooting you can visit EOSIO Documentation