Processing Smart Contracts (Compile Artifacts Demo)

Loading...

From the course by University at Buffalo

Smart Contracts

18 ratings

University at Buffalo

Smart Contracts

18 ratings

Course 2 of 4 in the Specialization Blockchain

This second course of the Blockchain specialization will help you design, code, deploy and execute a smart contract – the computational element of the blockchain technology. Smart contracts allow for implementing user-defined operations of arbitrary complexity that are not possible through plain cryptocurrency protocols. They allow users to implement conditions, rules and policies of the domain applications. Smart contracts are a powerful feature that, when properly designed and coded, can result in autonomous, efficient and transparent systems. You will design and program smart contracts in Solidity language, test and deploy them in the Remix development environment, and invoke them from a simple web interface that Remix provides. This course features best practices for designing solutions with smart contracts using Solidity and Remix IDE. Main concepts are delivered through videos, demos and hands-on exercises.

From the lesson

Smart Contract Basics

The purpose of this module is to introduce the reasons for a smart contract and its critical role in transforming blockchain technology from enabling decentralized systems. We will explore the structure and basic concepts of a smart contract through examples, and illustrate Remix (remix.ethereum.org) web IDE for deploying and interacting with a smart contract.

Processing Smart Contracts (Compile Artifacts Demo)4:52

Meet the Instructors

Bina Ramamurthy
Teaching Professor
Computer Science and Engineering Department

Module one, lesson three,

Processing a Smart Contract.

On completion of this lesson,

you will be able to explain the address of a smart contract,

list the compilation artifacts generated by the compiler: Bytecode,

ABI, web3deploy script, function hashes, and gas estimates.

A smart contract can be created on behalf of an externally owned a cog by application

pro-grammatically from the command line interface and by a script

of commands from high level applications and user interface or UI.

It can also be created from inside a smart contract.

We'll covered this approach in a later course.

We needed address for the smart contract to deploy it and invoke its functions.

The address is computed by hashing

the current number of externally owned account EOI and the notes.

Let us review these steps with the Greeter smart contract on remix.

Let's go back to the Greeter.sol and find out

how the compiler provides you many artifacts.

I'm going to compile and then click on the details button,

and you can see there is the name of the contract,

the metadata of the contract,

the bytecode of the smart contract that executes on

the Ethereum Virtual Machine.

The application binary interface is here.

And if you can expand on it,

you can see the radius details.

WebDeploy scripts is here.

This is used by the web application to interface to

a smart contract and the metadata hash.

And there are few other details on the function hashes,

the hashes by which the functions are called,

and the gas estimates when the functions are executed,

and the run time bytecode, and then the assembly code.

As you can see, a contract needs to be compiled and various artifacts are generated,

including the bytecode for deploying the contract and the application binary interface,

ABI, for the application that smart contract interact with the deployed bytecode.

Remix compiler script generates many artifacts in one shot.

You can view these items generated by clicking on

the compiled button and then the details button just below the compiled button.

A pop up screen appears with many details.

Here are some of the artifacts generated by

the remix smart contract compile process and their use.

ABI, application binary interface,

the interface Keima for transaction

to invoke functions on this smart contract instance bytecode.

Contract bytecode, this is the bytecode that is

executed for instantiating a smart contract on the EVM.

Think of it like executing a constructor of a smart contract to create an object.

WebDeploy script, this is two items, JSON script two,

web application to invoke smart contract function,

script for pro-grammatically deploying a smart contract from a web application.

Gass estimates, this provides a gas estimates

for deploying the smart contract and for the function invocation.

Function hashes, first four byte of

the function signatures to facilitate function invocation by a transaction.

Instance bytecode, the bytecode of the smart contract instance.

We will learn more about these and how to use them in

building block chain application in the upcoming lessons.

Summarizing, remix solidity compiler generates several artifacts as discussed.

Here are some important ones,

name of the contract,

bytecode executed for the contract creation on the EVM,

ABI: application binary interface,

details, functions, parameters and return values,

web3 deploy module that provides

the script for invoking the smart contract from web application,

gas estimates for execution of a function,

actual runtime bytecode of the smart contract.

Explore this list on remix ABI.

If you have remix window open and a smart contract on it,

click the compile and then the details button.

Explore our Catalog

Join for free and get personalized recommendations, updates and offers.

Coursera provides universal access to the world’s best education, partnering with top universities and organizations to offer courses online.

© 2018 Coursera Inc. All rights reserved.

Download on the App Store

Get it on Google Play