EOS Smart Contract Workshop

EOS Contract Development:

EOS Studio CEO: Phil

The EOS account system:

• Private key / public key
• Account: public key + system contract -> register the account
• owner: highest permission, can change activate
• activate:
• Account: occupies 4KB of resources (deploying contracts is free on the testnet)
• C++17
• CPU resources: requires staking tokens; refunded after 72 hours (gradually)

EOS Node Setup and Maintenance: EOSPark CTO: Specer

• Switch to the corresponding Tag and recompile
• Set -s

./eosio_build.sh -s EOS

• mongo plugin: avoid enabling the history plugin to save memory

Node configuration: + + +

EOSshenzhen CTO: Sheldon

• EOS official site
• EOS games
• Develope Telegram
• github.com/eosio
• eos.cdt
• eosio.contract
• eos-card-game-repo
• bancor
• eosio.token - learn to issue tokens
• boscore.io(BPFT)