Skip to main content

How to become a Blockchain developer and write your first Smart Contract - Part II

Introduction

Now that you've already learned the basic concepts needed to become a Blockchain developer, in our introductory article, and are more familiar with the entire ecosystem of tools needed, in this article we will see how to write and deploy our first Smart Contract using Solidity.

According to Solidity website:
Solidity is an object-oriented, high-level language for implementing smart contracts. Smart contracts are programs that govern the behavior of accounts within the Ethereum state.

Getting Started with the Solidity language

The easiest way to start writing your first Solidity Smart Contrat is using Remix an online Ethereum IDE.

To start creating your first Smart Contract you need to create a file with the .sol extension. So if you see a file with the .sol extension, that's a Smart Contract.

In Solidity we make use of a preprocessor directive to tell the compiler how to compile our code. Being a statically typed language, all types in our code will be checked in compile time as opposed to runtime. Another difference from other object-oriented languages is that you might be expecting to find the class keyword used to define a new class, but in Solidity we use the keyword contract instead. Since Solidity is influenced by other languages like JavaScript another difference we can notice is the use of the function keyword.

Below is a simple Smart Contract example that we can find in the Solidity website. Let's click on the "open in Remix" button to bring it's content to the Remix IDE so we can start calling some functions on it in order to better undesrtand how it works.

Notice in the image below the use of the .sol extension in the file name and the use of the keyword contract to define a Smart Contract.

How do we call functions in our Smart Contracts?

When you deploy a Smart Contract to an Ethereum network you will get back an address just like your own wallet address. You will then use this address to interact and invoke functions on it.

You will want first to deploy your Smart Contract to a local Blockchain Network using something like Ganache so that you can test your newly created Smart Contract.

Ethereum main public network is called Mainnet, but Ethereum also provide test networks called Testnets that you can use to test your Smart Contracts in a production-like environment.

We have a few icons in the left bar of Remix menu with among other things, options to: 
  1. Create a new workspace in the file explorer
  2. Configure and enable auto compilation
  3. Deploy and call the Smart Contract functions 
  4. Debugger 
  5. Plugin manager  
In the following image we can see we have opened the Solidity Compiler option where we can change the compiler version and toggle auto compilation on/off.
We are going to use the below version for compilation.
To start interacting with our Smart Contract we need to deploy our contract to one of the available environments. We can do that in the "DEPLOY & RUN TRANSACTIONS" section of the IDE. We will use the Remix VM from London as our sandbox running in the browser, as we can see from the image below.
In addition to the Environment option, we have 3 (three) more important configurations to make: the Account Address used to deploy the Smart Contract, the Gas Limit and the Contract which we want to deploy. Once we have all these options configured we can finally go and press the "Deploy" button.

You should be able to see an image similar to the one below showing 2 (two) buttons where we can call the functions in our Smart Contract. This is how we can interact and test our Smart Contract from inside the Remix IDE running in the browser. Since one of our functions expects to receive one parameter so we can set the value of the state variable storedData, the Remix IDE will place an input box right after the function button so we can pass the value to it.
You can see from the logs above, that I have already called the set function. If you open the debug section, in the bottom section of the IDE, you can also check all the information related to this transaction like it's status, transaction hash, block number, the amount of gas used, the transaction cost and the two account addresses involved in this transaction: the smart contract address and the caller address.
Let's now do a small change to our set function by multiplying every passed value by 2 (two) just so we can realize a few things. Click the "Deploy" button to deploy our new version with the change, but before that notice in the following image that we now have another contract, below our first contract, deployed to another address with our change. Also note that we now have 2 (two) versions of our contract deployed at 2 (two) different addresses that we can call functions with different implementations.
Let's now test our new function to see if the value is being multiplied by 2. You can see that we now have the value 80 below our get function button.

Conclusion

In the next article we are going to start using VS Code as our main IDE and the Truffle framework to test and deploy our Smart Contract.

References

Ethereum
Solidity
Ganache
Truffle Framework
MetaMask

Comments

Popular posts from this blog

How to use Splunk SPL commands to write better queries - Part I

Introduction As a software engineer, we are quite used to deal with logs in our daily lives, but in addition to ensuring that the necessary logs are being sent by the application itself or through a service mesh, we often have to go a little further and interact with some log tool to extract more meaningful data. This post is inspired by a problem I had to solve for a client who uses Splunk as their main data analysis tool and this is the first in a series of articles where we will delve deeper and learn how to use different Splunk commands. Running Splunk with Docker To run Splunk with docker, just run the following command: docker run -d —rm -p 8000:8000 -e SPLUNK_START_ARGS=--accept-license -e SPLUNK_PASSWORD=SOME_PASSWORD --name splunk splunk/splunk:latest Sample Data We are going to use the sample data provided by Splunk. You can find more information and download the zip file from their web site . How does it work? In order to be able to interact with Splunk t...

How to become a Blockchain developer and write your first Smart Contract

Introduction This is an introductory article to help you understanding the tools and frameworks needed so that you can know from where and how to start creating your own Smart Contracts. In this post I will give you an overview of the tools, frameworks, libraries and languages used to create a Smart Contract in the Ethereum Blockchain . In the second part of this article, we are going to see how to create a Smart Contracts using Solidity and ee are also going to see how to run a Blockchain locally using Ganache , so that you can deploy, interact and test your Smart Contract in your local development environment. According to a definition from the Wikipedia website: A blockchain is a decentralized, distributed, and often public, digital ledger consisting of records called blocks that are used to record transactions across many computers so that any involved block cannot be altered retroactively, without the alteration of all subsequent blocks.. What do you need to know? T...

How to run OPA in Docker

From the introduction of the openpolicyagent.org site: OPA generates policy decisions by evaluating the query input against policies and data. In this post i am going to show you an easy and fast way to test your policies by running OPA in Docker. First, make sure you have already installed Docker and have it running: docker ps Inside your choosen directory, create two files. One called input.json file for your system representation and one file called example.rego for your rego policy rules. Add the following content to your json file: Add the following content for the example.rego: Each violation block represents the rule that you want to validate your system against. The first violation block checks if any of the system servers have the http protocol in it. If that is the case, the server id is added to the array. In the same way, the second violation block checks for the servers that have the telnet protocol in it and if it finds a match the server id is also...