Smart Contract practices

Copyright © 2018 Nguyen Nguyen

Please never write code without tests

Lottery game

Designs can be found here

Contract url

Solidity basic knowledge

Solidity data type

Memory and storage

Array in Solidity

avoid nested array

static and dynamic array

Not allowed

bytes and string are special arrays

Functions

Function visibilities and modifier

Return multiple values

To assign results from multiple returns function to variable, we use tupple

Function overloading

Variable initialization

Mapping

Difference between mapping and hashtable (of java) or object (of javascript)

Mapping is defined as state , storage only, not allowed in function

Enum and struct are not a part of ABI definition, not available for external function call

Global variable:

Difference between msg.sender and tx.origin

Error handling in Solidity

No try-catch in Solidity

What happen if an exception is thrown

Check and handle exception

OOP Support

Inheritance: multiple inheritance is supported

Polimorphism

Overloading (except constructor)

Interface and abstract contract

Events and Logs

Events are part of ABI definition

Only indexed event arguments can be used in Filter, maximum 3 indices are allowed

Contract design patterns

Contract destruction

Sending tracsaction to dead contract: fail

ALl fund send to dead contract will be lost

Factory contract

Name registry pattern

Mapping iterator pattern

Use another array to keep keys

Storage cost goes up

Cost of iteration goes up

Withdrawal pattern

Send vs transfer

Withdrawal pattern

ERC-20 specification: 6 functions, 2 events

web3 knowledge

Send and Call

Filter object: web3.eth.filter

Event vs filter