Michael: Frontend developer with no backend experience

Smart Contract Development

According to solidity documentation, the 3 prerequisites of building a smart contract are understanding:

• accounts:: EoA(private key, trigger transaction, nunce: number of transactions already made since the creation of the account) and smart contract accounts(just public key the code acts as the private key it controls it)
• transactions: signed instruction from an account. The result is the changed state of the blockchain
• EVM: Ethereum Virtual Machine i.e where everything happens transactions, deployment

smart-contract: code that runs on the EVM. Languages are Solidity and Viper on the Ethereum blockchain. Solidity is a contract-based language i.e OOP all codes are written on the contract.

Smart contracts don’t execute themselves they have to be invoked. Transfer, withdraw. deposit...build something that simulates the EVM.

Blockchain is immutable i.e can’t change the history of the blockchain can declare a variable and assigned

low levels calls to send ether...you'll get results back either boolean won't revert. Callback data you get from smart contract call .get using low-level call

Don’t recommend using call data unless you’re sure of the gas fees you’ll use.

• function signatures(actually call function with low-level calls...using