If you have CPU resources available when you are not using your laptop or PC, then you can rent out your CPU power to a decentralized blockchain network. Someone who is in need of higher CPU usage would take your machine's CPU resources over the internet and, in return, pay you a small fee. For example, projects like Golem and iExec.
- Title Page
- Copyright and Credits
- Dedication
- About Packt
- Foreword
- Contributors
- Preface
- Section 1: Getting Started with Blockchain, Ethereum, and Solidity
- Introduction to Blockchain
- Understanding blockchain
- Blockchain solves the double-spending problem
- Properties of blockchain
- Distributed ledger
- Fault tolerance 
- Attack resistance
- Remove intermediaries
- Consensus protocol
- Faster settlement
- Lower transaction fees
- Transparency
- Immutability
- Irreversible transactions
- Trust in the network
- Availability
- Empower individuals
- Chronological order of transactions
- Timestamped
- Sealed with cryptography
- When to use blockchain
- When not to use blockchain
- Existing implementations of blockchain
- Introduction to Ethereum
- Smart contracts
- Summary
- Questions
- Understanding blockchain
- Getting Started with Solidity
- Introduction to the Solidity language
- Solidity data types
- Assigning variables with units
- Global special variables and functions
- Topics for self-study
- Summary
- Questions
- Further reading
- Control Structures and Contracts
- Section 2: Deep Dive into Development Tools
- Learning MetaMask and Remix
- Technical requirements
- Using the MetaMask plugin
- Using the Remix Solidity IDE
- The Remix IDE overview
- Compiler tools present under the Compile tab
- Understanding the Run tab
- Deploying a contract
- Initiating a transaction to execute the function
- Initiating a call to a view function and state variables
- Connecting the contract folder using remixd
- Setting up a local instance of the Remix IDE
- Using the blockchain explorer at etherscan.io
- Ethereum wallet software
- Using myetherwallet.com
- Summary
- Questions
- Using Ganache and the Truffle Framework
- Taking Advantage of Code Quality Tools
- Section 3: Mastering ERC Standards and Libraries
- ERC20 Token Standard
- Technical requirements
- Overview of the ERC20 token standard
- ERC20 standard API
- ERC20 implementation
- Events
- Optional functions
- Advanced functions
- Summary
- Questions
- ERC721 Non-Fungible Token Standard
- Technical requirements
- Overview of the ERC721 NFT standard
- The ERC721 NFT standard API interface
- Understanding the ERC721 implementation
- ERC721 inherits from IERC721 and ERC165
- Understanding ERC721 state variables
- Token owner mapping kept in _tokenOwner
- Approved address mapping kept in _tokenApprovals
- The number of tokens per owner kept in _ownedTokensCount
- Operator approvals kept in _operatorApprovals
- The ERC165 interface code for the ERC721, _INTERFACE_ID_ERC721
- The ERC165 interface code for the ERC721Receiver, _ERC721_RECEIVED
- The constructor of ERC721
- The balanceOf function
- The ownerOf function
- The approve function
- The getApproved function
- The setApprovalForAll function
- The isApprovedForAll function
- The transferFrom function
- The safeTransferFrom function
- Another safeTransferFrom function
- The _exists internal function
- The _isApprovedOrOwner internal function
- The _mint internal function
- The _burn internal function
- Another _burn internal function
- The _transferFrom internal function
- The _checkOnERC721Received internal function
- The _clearApproval internal function
- Events
- The ERC721TokenReceiver interface
- The ERC721Metadata interface
- The ERC721 enumerable
- The ERC721 full implementation
- Summary
- Questions
- Deep Dive into the OpenZeppelin Library
- Technical requirements
- The OpenZeppelin project 
- Contract ownership
- Roles library
- Life cycle contracts
- The ERC20 token standard library
- ERC20 interface – IERC20.sol
- Full ERC20 implementation using ERC20.sol
- Perform safe ERC20 function calls using SafeERC20.sol
- Create tokens with metadata using DetailedERC20.sol
- Create mintable tokens using ERC20Mintable.sol
- Allow token burning using ERC20Burnable.sol
- Create pausable tokens using ERC20Pausable.sol
- Math-related libraries
- Crowdsale
- Utility contracts
- Summary
- Questions
- Using Multisig Wallets
- Technical requirements
- Understanding multisig wallets
- Benefits of using multisig wallets
- Precautions when using multisig wallets
- Learning ConsenSys multisig implementation
- Setting up your own multisig wallet
- Sending ETH from a multisig contract
- Controlling contracts with multisig
- Summary
- Questions
- Upgradable Contracts Using ZeppelinOS
- Building Your Own Token
- Section 4: Design Patterns and Best Practices
- Solidity Design Patterns
- Tips, Tricks, and Security Best Practices
- Technical requirements
- Smart contracts best practices
- Avoiding floating pragma
- Avoid sharing a secret on-chain
- Be careful while using loops
- Avoid using tx.origin for authorization
- The timestamp can be manipulated by miners
- Carefully making external function calls
- Rounding errors with division
- Using assert(), require(), and revert() properly
- Gas consumption
- Known attack patterns
- Security analysis tools
- Summary
- Questions
- Assessments
- Other Books You May Enjoy
Decentralized computing
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.