• faucets don’t have storage

• reduce contract byte code: reduce deployment cost & runtime cost

• transaction runs out of gas cost i.e no gas cost

Etherscan

• reverted contract(red icon)

  • the address was expecting more than what it got so it was reverted. Despite reverting, the address owner still paid gas fees.

• the cache data structure in your mind it will be easy to deal with a contract. It's tentative to understand data structures.

• the best way to understand is interpreting contracts yourself. try to explain

• AAVE deals with math

• it can be as complex as possible

• contracts can be as cunny as possible. In your first role as a smart contract developer, you might not do something like this.

• function to encode a block of data into base64

 base64 of bytes

• code readability

Samples of Libraries

• Base64: encode & decode
• your job to pass the correct data structure: type IERC20. Understanding data structures help you achieve a lot of
• libraries are like tools or extensions. AAVE is a good example. libraries save gas as they use delegate calls and don’t have storage. You understand why delegate calls and why libraries use them as libraries don’t have storage. The specialty of libraries is to be used in contracts that don’t have storage
• Mostly done of NFT contracts it brings entrance.