This is a work more on concepts: we begin with a simple solidity contract. Then we walk through what happens during compilation and deployment, and how this contract is being accessed.

1. 3. Solidity Contract, Compilation and
Deployment (Concept)
KC Tam
Reach KC on LinkedIn: https://www.linkedin.com/in/ktam1/

2. Objective
We first take a glimpse in the SimpleStorage Contract and
understand a bit how Solidity Contract looks like. Then we
will get some ideas on contract compilation and deployment,
and how application is accessing the deployed contract.

3. A Typical Solidity Contract
Human readable
Define the business logic we wish to implement in Ethereum Network (remember,
this is just a giant computer)
A Solidity Contract is roughly composed of these parts,
● Solidity version for proper compilation
● Variables and data structures storing data
● Functions to process the data

4. pragma solidity ^0.4.0;
contract SimpleStorage {
uint storedData;
function set(uint x) public {
storedData = x;
}
function get() constant public returns (uint retVal) {
return storedData;
}
}
Source: https://solidity.readthedocs.io/en/develop/introduction-to-smart-contracts.html
Contract name
SimpleStorage
variable storedData in Ethereum
Network that stores the value
function set(x) to modify the value
of storedData stored in the
Ethereum Network
function get() to retrieve the value
of storedData stored in the
Ethereum Network
Solidity Contract

5. Gigantic Computer
Contract
code in
Solidity
Artifacts
(Bytecode
and ABI)
Deployed
Contract
(accessible)
Compile Deploy
Web / Mobile Frontend
Access

6. Contract Code in
Solidity
artifact
ABI
Bytecode
Compilation
Bytecode: machine-readable code to be deployed on Ethereum Network
Application Binary Interface (ABI): the interface between application
and bytecode deployed on Ethereum Network
Compile

7. Artifact of SimpleStorage
ABI
[{"constant":false,"inputs":[{"name":"x","type":"uint256"}],"name":"set","outputs
":[],"payable":false,"stateMutability":"nonpayable","type":"function"},{"constant
":true,"inputs":[],"name":"get","outputs":[{"name":"retVal","type":"uint256"}],"pa
yable":false,"stateMutability":"view","type":"function"}]
Bytecode
"6060604052341561000f57600080fd5b60d38061001d6000396000f3006060
604052600436106049576000357c010000000000000000000000000000000
0000000000000000000000000900463ffffffff16806360fe47b114604e5780636
d4ce63c14606e575b600080fd5b3415605857600080fd5b606c600480803590
60200190919050506094565b005b3415607857600080fd5b607e609e565b60
40518082815260200191505060405180910390f35b8060008190555050565b
600080549050905600a165627a7a72305820aa1702bf13d58014043cd19825
b6024d08ca61876e492bd169a100f816489ea90029"
Note: Compiled contract code (artifact) is NOT deployed yet. It cannot be used or accessed
until it is deployed on an Ethereum Network and a Contract Address is obtained.

8. Ethereum Network (the Giant Computer)
artifact
ABI
Bytecode
Contract Deployment
● Artifact is deployed on an Ethereum
Network.
● An address (Contract Address) is given to
this deployed contract.
● Deployed contract is identified by this
Contract Address.
Deployed Contract
Bytecode
ABI
Contract
Address
Deploy

9. Ethereum Network (the Giant Computer)
artifact
ABI
Bytecode
Contract Deployment
● An artifact can be deployed as many times
as one wishes.
● This newly deployed contract is given with a
different Contract Address.
● These contracts are isolated to one
another.
Deployed Contract
Bytecode
ABI
Contract
Address
Deploy
Deployed Contract
Bytecode
Contract
Address
ABI

10. Ethereum Network (the Giant Computer)
Access Contract
● Frontend accesses the deployed contract
through Contract Address.
● With ABI well defined, frontend can access
variables and execute contract functions in
this deployed contract.
Deployed Contract
Bytecode
ABI
Contract
Address
Web / Mobile Frontend
Contract AddressABI
Access

11. Summary
We have seen how a simple Solidity contract looks like. We
also covered the concepts of code compilation and
deployment on Ethereum Network, and how frontend
accesses the deployed contract.