Please enable JavaScript.

Coggle requires JavaScript to display documents.

Solidity Study Notes (Theories (Storage (Stack (temp) (This only can…

- - - - Supper expansive
        
        20000 to create an address and 5000 to modify it.
      - Using storage key word after the declaration of the variable in the function declaration line
    - - This only can easily assess the top 16 items, and compiler will fail if the request is more than that. Normally for scratch purposes (leave that for the compiler)
      - Erased after contract terminaltion
      - Almost free
    - - 3 gas for each call when the size is small, but will grow quadratically if the size is large: say MB, will request millions of gases
      - Erased after contract termination
  - - - From
      - Target
      - Payload
      - Gas
      - Ether
      - Return data
    - - Everything stays the same as in the original message call, except the context/script of the contract is borrowed from another contract. This enables the library functionality in Solidity.
      - Conceptually the same as using library/packages from other source
  - - - Just change some internal states to make the contract revert all received Ether
    - - By the implemented selfdestruct function
      - By delegatecall or callcode
      - :warning: All the ether send to this address will be lost!!!
      - However, all the contract and historical codes are still on the world state, thus not the same as harddisk remove.
      - Just import "mortal" on top of the contract, and then the kill() will take care of everything.
  - - - bytes(s)[i] = c
- - - - function minter() external view returns (address) { return minter; }