Resources

EOS.IO - The Most Powerful Infrastructure for Decentralized Applications

Welcome to the EOS.IO source code repository! EOS.IO software enables developers to create and deploy high-performance, horizontally scalable, blockchain infrastructure upon which decentralized applications can be built.

This code is currently alpha-quality and under rapid development. That said, there is plenty early experimenters can do including, running a private multi-node test network and develop applications (smart contracts).

Resources

Getting Started
Setting up a build/development environment
1. Automated build script
  1. Clean install Ubuntu 16.10
  2. MacOS Sierra 10.12.6
Building EOS and running a node
Example Currency Contract Walkthrough
Running local testnet
Doxygen documentation
Running EOS in Docker
Manual installation of the dependencies
1. Clean install Ubuntu 16.10
2. MacOS Sierra 10.12.6

Getting Started

The following instructions overview the process of getting the software, building it, running a simple test network that produces blocks, account creation and uploading a sample contract to the blockchain.

Setting up a build/development environment

Automated build script

For Ubuntu 16.10 and MacOS Sierra, there is an automated build script that can install all dependencies and builds EOS.

It is called build.sh with following inputs.

architecture [ubuntu|darwin]
optional mode [full|build]

The second optional input can be full or build where full implies that it installs dependencies and builds eos. If you omit this input then build script always installs dependencies and then builds eos.

./build.sh <architecture> <optional mode>

Clone EOS repository recursively as below and run build.sh located in root eos folder.

Clean install Ubuntu 16.10

git clone https://github.com/eosio/eos --recursive

cd eos
./build.sh ubuntu

Now you can proceed to the next step - Creating and launching a single-node testnet

MacOS Sierra

Before running the script make sure you have updated XCode and brew:

xcode-select --install
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

git clone https://github.com/eosio/eos --recursive

cd eos
./build.sh darwin

Now you can proceed to the next step - Creating and launching a single-node testnet

Building EOS and running a node

Getting the code

To download all of the code, download EOS source code and a recursion or two of submodules. The easiest way to get all of this is to do a recursive clone:

git clone https://github.com/eosio/eos --recursive

If a repo is cloned without the --recursive flag, the submodules can be retrieved after the fact by running this command from within the repo:

git submodule update --init --recursive

Building from source code

The WASM_LLVM_CONFIG environment variable is used to find our recently built WASM compiler. This is needed to compile the example contracts inside eos/contracts folder and their respective tests.

cd ~
git clone https://github.com/eosio/eos --recursive
mkdir -p ~/eos/build && cd ~/eos/build
cmake -DBINARYEN_BIN=~/binaryen/bin -DOPENSSL_ROOT_DIR=/usr/local/opt/openssl -DOPENSSL_LIBRARIES=/usr/local/opt/openssl/lib ..
make -j4

Out-of-source builds are also supported. To override clang's default choice in compiler, add these flags to the CMake command:

-DCMAKE_CXX_COMPILER=/path/to/c++ -DCMAKE_C_COMPILER=/path/to/cc

For a debug build, add -DCMAKE_BUILD_TYPE=Debug. Other common build types include Release and RelWithDebInfo.

To run the test suite after building, run the chain_test executable in the tests folder.

EOS comes with a number of programs you can find in ~/eos/build/programs. They are listed below:

eosd - server-side blockchain node component
eosc - command line interface to interact with the blockchain
eos-walletd - EOS wallet
launcher - application for nodes network composing and deployment; more on launcher

Creating and launching a single-node testnet

After successfully building the project, the eosd binary should be present in the build/programs/eosd directory. Go ahead and run eosd -- it will probably exit with an error, but if not, close it immediately with Ctrl-C. Note that eosd created a directory named data-dir containing the default configuration (config.ini) and some other internals. This default data storage path can be overridden by passing --data-dir /path/to/data to eosd.

Edit the config.ini file, adding/updating the following settings to the defaults already in place:

# Load the testnet genesis state, which creates some initial block producers with the default key
genesis-json = /path/to/eos/source/genesis.json
 # Enable production on a stale chain, since a single-node test chain is pretty much always stale
enable-stale-production = true
# Enable block production with the testnet producers
producer-name = inita
producer-name = initb
producer-name = initc
producer-name = initd
producer-name = inite
producer-name = initf
producer-name = initg
producer-name = inith
producer-name = initi
producer-name = initj
producer-name = initk
producer-name = initl
producer-name = initm
producer-name = initn
producer-name = inito
producer-name = initp
producer-name = initq
producer-name = initr
producer-name = inits
producer-name = initt
producer-name = initu
# Load the block producer plugin, so you can produce blocks
plugin = eosio::producer_plugin
# Wallet plugin
plugin = eosio::wallet_api_plugin
# As well as API and HTTP plugins
plugin = eosio::chain_api_plugin
plugin = eosio::http_plugin

Now it should be possible to run eosd and see it begin producing blocks.

When running eosd you should get log messages similar to below. It means the blocks are successfully produced.

1575001ms thread-0   chain_controller.cpp:235      _push_block          ] initm #1 @2017-09-04T04:26:15  | 0 trx, 0 pending, exectime_ms=0
1575001ms thread-0   producer_plugin.cpp:207       block_production_loo ] initm generated block #1 @ 2017-09-04T04:26:15 with 0 trxs  0 pending
1578001ms thread-0   chain_controller.cpp:235      _push_block          ] initc #2 @2017-09-04T04:26:18  | 0 trx, 0 pending, exectime_ms=0
1578001ms thread-0   producer_plugin.cpp:207       block_production_loo ] initc generated block #2 @ 2017-09-04T04:26:18 with 0 trxs  0 pending
...

Example "Currency" Contract Walkthrough

EOS comes with example contracts that can be uploaded and run for testing purposes. Next we demonstrate how to upload and interact with the sample contract "currency".

Example smart contracts

First, run the node

cd ~/eos/build/programs/eosd/
./eosd

Setting up a wallet and importing account key

As you've previously added plugin = eosio::wallet_api_plugin into config.ini, EOS wallet will be running as a part of eosd process. Every contract requires an associated account, so first, create a wallet.

cd ~/eos/build/programs/eosc/
./eosc wallet create # Outputs a password that you need to save to be able to lock/unlock the wallet

For the purpose of this walkthrough, import the private key of the inita account, a test account included within genesis.json, so that you're able to issue API commands under authority of an existing account. The private key referenced below is found within your config.ini and is provided to you for testing purposes.

./eosc wallet import 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3

Creating accounts for sample "currency" contract

First, generate some public/private key pairs that will be later assigned as owner_key and active_key.

cd ~/eos/build/programs/eosc/
./eosc create key # owner_key
./eosc create key # active_key

This will output two pairs of public and private keys

Private key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Public key: EOSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Important: Save the values for future reference.

Run the create command where inita is the account authorizing the creation of the currency account and PUBLIC_KEY_1 and PUBLIC_KEY_2 are the values generated by the create key command

./eosc create account inita currency PUBLIC_KEY_1 PUBLIC_KEY_2

You should then get a json response back with a transaction ID confirming it was executed successfully.

Go ahead and check that the account was successfully created

./eosc get account currency

If all went well, you will receive output similar to the following

{
  "account_name": "currency",
  "eos_balance": "0.0000 EOS",
  "staked_balance": "0.0001 EOS",
  "unstaking_balance": "0.0000 EOS",
  "last_unstaking_time": "1969-12-31T23:59:59",
  "permissions": [{
    ...
    }
  ]
}

Now import the active private key generated previously in the wallet:

./eosc wallet import XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Upload sample "currency" contract to blockchain

Before uploading a contract, verify that there is no current contract:

./eosc get code currency 
code hash: 0000000000000000000000000000000000000000000000000000000000000000

With an account for a contract created, upload a sample contract:

./eosc set contract currency ../../contracts/currency/currency.wast ../../contracts/currency/currency.abi

As a response you should get a json with a transaction_id field. Your contract was successfully uploaded!

You can also verify that the code has been set with the following command

./eosc get code currency

It will return something like

code hash: 9b9db1a7940503a88535517049e64467a6e8f4e9e03af15e9968ec89dd794975

Next verify the currency contract has the proper initial balance:

./eosc get table currency currency account
{
  "rows": [{
     "key": "account",
     "balance": 1000000000
     }
  ],
  "more": false
}

Transfering funds with the sample "currency" contract

Anyone can send any message to any contract at any time, but the contracts may reject messages which are not given necessary permission. Messages are not sent "from" anyone, they are sent "with permission of" one or more accounts and permission levels. The following commands shows a "transfer" message being sent to the "currency" contract.

The content of the message is '{"from":"currency","to":"inita","quantity":50}'. In this case we are asking the currency contract to transfer funds from itself to someone else. This requires the permission of the currency contract.

./eosc push message currency transfer '{"from":"currency","to":"inita","quantity":50}' --scope currency,inita --permission currency@active

Below is a generalization that shows the currency account is only referenced once, to specify which contract to deliver the transfer message to.

./eosc push message currency transfer '{"from":"${usera}","to":"${userb}","quantity":50}' --scope ${usera},${userb} --permission ${usera}@active

We specify the --scope ... argument to give the currency contract read/write permission to those users so it can modify their balances. In a future release scope will be determined automatically.

As a confirmation of a successfully submitted transaction you will receive json output that includes a transaction_id field.

Reading sample "currency" contract balance

So now check the state of both of the accounts involved in the previous transaction.

./eosc get table inita currency account
{
  "rows": [{
      "key": "account",
      "balance": 50 
       }
    ],
  "more": false
}
./eosc get table currency currency account
{
  "rows": [{
      "key": "account",
      "balance": 999999950
    }
  ],
  "more": false
}

As expected, the receiving account inita now has a balance of 50 tokens, and the sending account now has 50 less tokens than its initial supply.

Running multi-node local testnet

To run a local testnet you can use a launcher application provided in ~/eos/build/programs/launcher folder.

For testing purposes you will run 2 local production nodes talking to each other.

cd ~/eos/build
cp ../genesis.json ./
./programs/launcher/launcher -p2 --skip-signature

This command will generate 2 data folders for each instance of the node: tn_data_0 and tn_data_1.

You should see a following response:

adding hostname ip-XXX-XXX-XXX
found interface 127.0.0.1
found interface XXX.XX.XX.XX
spawning child, programs/eosd/eosd --skip-transaction-signatures --data-dir tn_data_0
spawning child, programs/eosd/eosd --skip-transaction-signatures --data-dir tn_data_1

To confirm the nodes are running, run following eosc commands:

~/eos/build/programs/eosc
./eosc -p 8888 get info
./eosc -p 8889 get info

For each you should get a json with a blockchain information.

You can read more on launcher and its settings here

Doxygen documentation

You can find more detailed API documentation in Doxygen reference: https://eosio.github.io/eos/

Running EOS in Docker

You can find up to date information about EOS Docker in the Docker Readme

Manual installation of the dependencies

If you prefer to manually build dependencies - follow the steps below.

This project is written primarily in C++14 and uses CMake as its build system. An up-to-date Clang and the latest version of CMake is recommended.

Dependencies:

Clang 4.0.0
CMake 3.5.1
Boost 1.64
OpenSSL
LLVM 4.0
secp256k1-zkp (Cryptonomex branch)
binaryen

Clean install Ubuntu 16.10

Install the development toolkit:

sudo apt-get update
wget -O - https://apt.llvm.org/llvm-snapshot.gpg.key|sudo apt-key add -
sudo apt-get install clang-4.0 lldb-4.0 libclang-4.0-dev cmake make \
                     libbz2-dev libssl-dev libgmp3-dev \
                     autotools-dev build-essential \
                     libbz2-dev libicu-dev python-dev \
                     autoconf libtool git

Install Boost 1.64:

cd ~
wget -c 'https://sourceforge.net/projects/boost/files/boost/1.64.0/boost_1_64_0.tar.bz2/download' -O boost_1.64.0.tar.bz2
tar xjf boost_1.64.0.tar.bz2
cd boost_1_64_0/
echo "export BOOST_ROOT=$HOME/opt/boost_1_64_0" >> ~/.bash_profile
source ~/.bash_profile
./bootstrap.sh "--prefix=$BOOST_ROOT"
./b2 install
source ~/.bash_profile

Install secp256k1-zkp (Cryptonomex branch):

cd ~
git clone https://github.com/cryptonomex/secp256k1-zkp.git
cd secp256k1-zkp
./autogen.sh
./configure
make
sudo make install

To use the WASM compiler, EOS has an external dependency on binaryen:

cd ~
git clone https://github.com/WebAssembly/binaryen.git
cd ~/binaryen
git checkout tags/1.37.14
cmake . && make

Add BINARYEN_ROOT to your .bash_profile:

echo "export BINARYEN_ROOT=~/binaryen" >> ~/.bash_profile
source ~/.bash_profile

By default LLVM and clang do not include the WASM build target, so you will have to build it yourself:

mkdir  ~/wasm-compiler
cd ~/wasm-compiler
git clone --depth 1 --single-branch --branch release_40 https://github.com/llvm-mirror/llvm.git
cd llvm/tools
git clone --depth 1 --single-branch --branch release_40 https://github.com/llvm-mirror/clang.git
cd ..
mkdir build
cd build
cmake -G "Unix Makefiles" -DCMAKE_INSTALL_PREFIX=.. -DLLVM_TARGETS_TO_BUILD= -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly -DCMAKE_BUILD_TYPE=Release ../
make -j4 install

Your environment is set up. Now you can build EOS and run a node.

MacOS Sierra 10.12.6

macOS additional Dependencies:

Brew
Newest XCode

Upgrade your XCode to the newest version:

xcode-select --install

Install homebrew:

ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

Install the dependencies:

brew update
brew install git automake libtool boost openssl llvm@4 gmp ninja gettext
brew link gettext --force

Install secp256k1-zkp (Cryptonomex branch):

cd ~
git clone https://github.com/cryptonomex/secp256k1-zkp.git
cd secp256k1-zkp
./autogen.sh
./configure
make
sudo make install

Install binaryen v1.37.14:

cd ~
git clone https://github.com/WebAssembly/binaryen.git
cd ~/binaryen
git checkout tags/1.37.14
cmake . && make

Add BINARYEN_ROOT to your .bash_profile:

echo "export BINARYEN_ROOT=~/binaryen" >> ~/.bash_profile
source ~/.bash_profile

Build LLVM and clang for WASM:

mkdir  ~/wasm-compiler
cd ~/wasm-compiler
git clone --depth 1 --single-branch --branch release_40 https://github.com/llvm-mirror/llvm.git
cd llvm/tools
git clone --depth 1 --single-branch --branch release_40 https://github.com/llvm-mirror/clang.git
cd ..
mkdir build
cd build
cmake -G "Unix Makefiles" -DCMAKE_INSTALL_PREFIX=.. -DLLVM_TARGETS_TO_BUILD= -DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=WebAssembly -DCMAKE_BUILD_TYPE=Release ../
make -j4 install

Add WASM_LLVM_CONFIG and LLVM_DIR to your .bash_profile:

echo "export WASM_LLVM_CONFIG=~/wasm-compiler/llvm/bin/llvm-config" >> ~/.bash_profile
echo "export LLVM_DIR=/usr/local/Cellar/llvm/4.0.1/lib/cmake/llvm" >> ~/.bash_profile
source ~/.bash_profile

Name		Name	Last commit message	Last commit date
Latest commit History 1,778 Commits
CMakeModules		CMakeModules
Docker		Docker
contracts		contracts
docs		docs
libraries		libraries
plugins		plugins
programs		programs
scripts		scripts
tests		tests
tools		tools
.gitignore		.gitignore
.gitlab-ci.yml		.gitlab-ci.yml
.gitmodules		.gitmodules
.travis.yml		.travis.yml
AUTOMATED_ABI_GENERATOR.md		AUTOMATED_ABI_GENERATOR.md
CMakeLists.txt		CMakeLists.txt
CONTRACT_DEVELOPER_API.md		CONTRACT_DEVELOPER_API.md
DOXYGEN_GUIDELINES.md		DOXYGEN_GUIDELINES.md
Doxyfile		Doxyfile
GITHUB_USAGE_PROCESS.md		GITHUB_USAGE_PROCESS.md
HEADER		HEADER
LICENSE.txt		LICENSE.txt
README.md		README.md
build.sh		build.sh
circle.yml		circle.yml
eos-logo.png		eos-logo.png
eos.doxygen.in		eos.doxygen.in
genesis.json		genesis.json
mesh.dot		mesh.dot
mesh.png		mesh.png
ring.dot		ring.dot
ring.png		ring.png
star.dot		star.dot
star.png		star.png
testnet-diagrams.sh		testnet-diagrams.sh
testnet.md		testnet.md

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

EOS.IO - The Most Powerful Infrastructure for Decentralized Applications

Resources

Table of contents

Getting Started

Setting up a build/development environment

Automated build script

Clean install Ubuntu 16.10

MacOS Sierra

Building EOS and running a node

Getting the code

Building from source code

Creating and launching a single-node testnet

Example "Currency" Contract Walkthrough

Example smart contracts

Setting up a wallet and importing account key

Creating accounts for sample "currency" contract

Upload sample "currency" contract to blockchain

Transfering funds with the sample "currency" contract

Reading sample "currency" contract balance

Running multi-node local testnet

Doxygen documentation

Running EOS in Docker

Manual installation of the dependencies

Clean install Ubuntu 16.10

MacOS Sierra 10.12.6

About

Releases

Packages

Languages

License

theultimatum/eos

Folders and files

Latest commit

History

Repository files navigation

EOS.IO - The Most Powerful Infrastructure for Decentralized Applications

Resources

Table of contents

Getting Started

Setting up a build/development environment

Automated build script

Clean install Ubuntu 16.10

MacOS Sierra

Building EOS and running a node

Getting the code

Building from source code

Creating and launching a single-node testnet

Example "Currency" Contract Walkthrough

Example smart contracts

Setting up a wallet and importing account key

Creating accounts for sample "currency" contract

Upload sample "currency" contract to blockchain

Transfering funds with the sample "currency" contract

Reading sample "currency" contract balance

Running multi-node local testnet

Doxygen documentation

Running EOS in Docker

Manual installation of the dependencies

Clean install Ubuntu 16.10

MacOS Sierra 10.12.6

About

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages