Getting Started

The eos Developer Hub

Welcome to the eos developer hub. You'll find comprehensive guides and documentation to help you start working with eos as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Discussions

1.2 Before You Begin

Looking for the version of this series that uses Docker?

Step 1: Install binaries

This tutorial is going to use pre-built binaries. For you to get started as quickly as possible this is the best option. Building from source is a more advanced option but will set you back an hour or more and you may encounter build errors.

You can find how to build EOSIO from source here.

The below commands will download binaries for respective operating systems.

Mac OS X Brew Install:

brew tap eosio/eosio
brew install eosio

If you don't have Brew installed, follow the installation instructions on the official Brew website.

Ubuntu 18.04 Debian Package Install:


sudo apt install ./eosio_2.0.0-1-ubuntu-18.04_amd64.deb

Ubuntu 16.04 Debian Package Install:


sudo apt install ./eosio_1.8.6-1-ubuntu-16.04_amd64.deb

CentOS RPM Package Install:


sudo yum install ./eosio-2.0.0-1.el7.x86_64.rpm

If you have previous versions of eosio installed on your system, please uninstall before proceeding. Detail instruction see here

Step 2: Setup a development directory, stick to it.

You're going to need to pick a directory to work from, it's suggested to create a contracts directory somewhere on your local drive.

mkdir contracts
cd contracts

Step 3: Enter your local directory below.

Get the path of that directory and save it for later, as you're going to need it, you can use the following command to get your absolute path.


Enter the absolute path to your contract directory below, and it will be inserted throughout the documentation to make your life a bit easier. This functionality requires cookies

Updated 8 days ago

1.2 Before You Begin

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.