Address - payable: send operation & transfer operation.
Address.auth
this.transfer
//inbuilt functionality
- generative NFT project
- NatSpec Format is a way to comment on code on solidity and the EVM understands it. It's a special form of comments to provide rich documentation for functions, return variables, and more. This special form is named the Ethereum Natural Language Specification Format (NatSpec).
almost like key-value types in Javascript:
- balance
- transfer
<address>.balance //uint256
<address>.code // bytes memory
<address>.codehash // bytes32
<address>.payable.transfer(uint256 amount)
<address payable>.transfer(uint256 amount) returns (bool)
<address>.call(bytes memory) returns (bool, bytes memory)
<address>.delegatecall(bytes memory) returns (bool, bytes memory)
- Balance
- Transfer function fails if the balance of the current contract is not large enough or if Ether transfer is rejected by receiving account. The transfer functions revert to failure to transfer.
- send is the low-level counterpart of transfer. If execution fails the current contract will not stop with an exception but send will
- View & Pure can’t modify the state variables. The view can read state variables on your contract and pure can’t. They cost gas coz they can’t modify the state. Making it Turing Complete
- What are the use cases for bit operators and shift functions: use them to deal with data types on a hit level. You’ll know when you need it.
With documentation know the basics you don’t have to read the entire thing but understand the basics of solidity.
People to follow on Twitter