<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=2258763691017137&amp;ev=PageView&amp;noscript=1">
Simplex Software
hello eos

EOS.IO is the first-to-market, enterprise-ready, third-generation Blockchain. It aims to become a decentralized operating system supporting industrial-scale applications, eliminating transaction fees and being able to conduct millions of transactions per second.

EOS.IO takes smart contracts to the next level, operating as a smart contract platform. In this article we will learn its basics.

Running our private node

In order to deploy our first “Hello world!” smart contract we are going to need at least one EOS node running. We will communicate with this node via CLI and provide the smart contract to be deployed. Please note that this requires to have EOS installed. You can see how to do that here.

Start your node

You can start your node using this single command:

$ nodeos -e -p eosio --plugin eosio::chain_api_plugin --plugin eosio::history_api_plugin

This will show an output as the following


This is a notifying message, each half a second duration, showing that a new block has been produced and confirming that the node is up and running.

Cleos and wallet creation

cleos command is our friend. This CLI application allows us to communicate with our node, create wallets, ask for balance, transfer money, and so much more.

In order set a contract to an account, we need to have the required permissions. Since in this example we are going to be using the eosio account (the EOS’s root account), we already have these permissions. But we do need to sign the transaction, and to do this, we need eosio’s private key. To use this private key we need to ensure we have it in our wallet, and for this, my friends… we need a wallet.

$ cleos wallet create

The above command creates our default wallet, the standard output then showing its password. Save it! You will need this password in order to unlock the wallet.

This command creates our default wallet, showing the password via standard output.

Importing keys

You can think of a wallet as a keyring, it keeps all of our keys organized in one place. So, this is why we create it, to keep our eosio’s private key to sign our transactions validating that we have the required permissions. Now, we import the eosio’s private key.

$ cleos wallet import 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3

The one above is the public domain key. If you have changed the eosio’s public key, replace it with the corresponding private key.

Hello World!

Having the required key in our wallet, we can now focus on our smart contract code. For the sake of simplicity, we will write a simple Hello World smart contract.

Let’s create a hello.cpp file with the following content:

1  #include <eosiolib/eosio.hpp>
2  using namespace eosio;
4  class hello : public eosio::contract {
5    public:
6    using contract::contract;
8    /// @abi action
9    void hi() {
10     print( "Hello world!");
11   }
12 };
14 EOSIO_ABI( hello, (hi) )

Code analysis

1 #include

Is the header for EOS’s smart contracts.

4 class hello : public eosio::contract {

Declares hello class as a eosiio::contract derived.

8 /// @abi action
9 void hi() {

Declares hi() function as part of the contract’s ABI.

10 print( "Hello World!");

Prints Hello World! on calling hi.

14 EOSIO_ABI( hello, (hi) )

It is the ABI declaration of our smart contract, so it must include all the actions (class methods) that we want to potentially get called on it. It is the json to binary (and reverse) bridge. This macro also calls apply() on the contract.


The next step is to compile the contract. For this we will use the EOS’s eosiocpp script with the following parameters:

$ eosiocpp -o hello.wast hello.cpp

This will compile our C++ code into WebAssembly, resulting on a hello.wast file.

And then

$ eosiocpp -g hello.abi hello.cpp

Which will create a hello.abi file with the ABI declaration of our contract.

Both file are required to deploy the Hello Word! smart contract.

Deploying the smart contract

Finally, the last step is to deploy our smart contract to the blockchain. The command to do this has the following format:

cleos set contract <account to deploy to> <contract path> <contract name>.wast <contract name>.abi

So we have:

$ cleos set contract eosio . hello.wast hello.abi


We can verify that our smart contract is responding to us by calling on this:

$ cleos push action eosio hi ’’ -p eosio

Here we send an action to eosio, the user we have previously deployed the contract with, calling the action hi without parameters. Then we sign on with our private key (-p eosio), used earlier in one of our previous steps.


Creating a smart contract for EOS is easy. You must have a wallet, and have imported the user-key signing the transaction. Then just write the smart contract, compile and deploy it to the blockchain.

And that’s all, folks!

Follow Us

Subscribe To Our Blog

Let Us Know What You Thought about this Post.

Put your Comment Below.