Add new content

Author: davidekete

Basics/README.md

@@ -1,3 +1,3 @@
 ## Loading, Compiling, Deploying
 
-This beginner level tutorial introduces Remix's interface and concepts used in Ethereum. 
+This beginner level tutorial introduces Remix's interface and concepts used in Ethereum.

Intro-to-blockchain-and-ethereum/README.md

@@ -0,0 +1 @@
+This section is a primer of Web3 concepts you will encounter. It covers what a blockchain is, a primer on the EVM, Ethereum accounts, transactions, gas, etc.

Intro-to-blockchain-and-ethereum/config.yml

@@ -0,0 +1,12 @@
+---
+id: intro-blockchain
+name: An introduction to the Blockchain and Ethereum
+summary: Understand the blockchain and how it works from the Ethereum perspective
+level: 1
+tags:
+  - Blockchain
+steps:
+  - name: Introduction to the Blockchain (for Developers)
+    path: intro-to-blockchain
+  - name: Introduction to the Ethereum Virtual Machine (EVM)
+    path: intro-to-evm

Intro-to-blockchain-and-ethereum/intro-to-blockchain/README.md

@@ -0,0 +1,31 @@
+A blockchain is an append-only ledger shared across many computers (nodes). Unlike a traditional database, you never edit or delete past entries; you can only add new entries that, together, define the latest state.
+
+On public blockchains (some blockchains are private), identical copies of this ledger are widely replicated, and nodes accept new data only if it satisfies the network’s consensus rules.
+
+## How blockchains work
+
+At a high level, three parts cooperate: an execution layer that deterministically turns transactions into state changes, a consensus mechanism that orders blocks and decides what becomes canonical, and data availability/state so everyone can fetch and verify the data. When these are aligned, immutability is the practical outcome and rewriting history becomes economically prohibitive.
+
+### Consensus mechanism
+
+A consensus mechanism is how the network agrees on the next valid block. For example, **proof-of-stake**, where validators bond capital and can be slashed, and or **proof-of-work**, where miners prove computational effort.
+
+### Execution Layer
+
+The execution layer defines how transactions are interpreted and applied to state, step by step, the same way on every node. For example, on EVM chains (Ethereum and many L2s), contracts compile to EVM bytecode.
+
+Note: Execution is separate from consensus; a network can change how it reaches agreement without changing how code runs, and vice versa.
+
+### State changes
+
+Users submit signed transactions that describe intended changes (transfer value, call a contract). Nodes execute these deterministically and, if valid, include them in blocks that extend the chain.
+
+### Immutability
+
+Immutability isn’t “forbidden by code”; it’s economically enforced. On Ethereum, blocks become finalized when ≈ two-thirds of staked validators attest to the relevant checkpoints. Reverting a finalized block would require creating conflicting finality—an act that implies slashing at least one-third of the total staked ETH. With roughly ~35–36 million ETH staked today, that’s on the order of ≥11–12 million ETH at risk, which makes rewriting finalized history prohibitively costly.
+
+## Further reading
+
+- [Web2 vs. Web3](https://ethereum.org/developers/docs/web2-vs-web3/).
+- [An introduction to blockchain and Ethereum](https://ethereum.org/developers/docs/intro-to-ethereum/).
+- [Consensus algorithms in blockchains](https://www.geeksforgeeks.org/compiler-design/consensus-algorithms-in-blockchain/).

Intro-to-blockchain-and-ethereum/intro-to-evm/README.md

@@ -0,0 +1,18 @@
+The **Ethereum Virtual Machine (EVM)** is the engine that turns transactions into changes on Ethereum and other EVM-compatible chains.
+
+It’s not one server. It’s a set of rules (a specification). Every node follows the same rules so that, with the same inputs, they all get the same result. The EVM defines what a smart contract can do, how data is stored, what operations exist, and how much those operations cost.
+
+## How the EVM works
+
+A user signs a transaction in a wallet and sends it to the network. A node checks that the signature is valid, that the account’s order number (nonce) is correct, and that the account can afford the maximum cost. The node then hands the transaction to the EVM with a gas limit.
+
+Gas is the fee paid for computational work on Ethereum. It is paid in ETH (usually quoted in gwei), and a gas limit is the maximum number of gas units you allow the transaction to consume.
+
+The EVM runs the contract code step by step. Each step uses some gas. If execution succeeds, the contract’s stored data (state) is updated and the transaction can emit events that your app can later read. If execution fails, the state changes are rolled back, but the gas used up to that point will not be refunded.
+
+When it’s done, the node returns a receipt. The receipt says whether the transaction succeeded, how much gas it used, which events were emitted, and, if you deployed a contract, the new contract address.
+
+## Further Reading
+
+- [The Ethereum virtual machine](https://ethereum.org/developers/docs/evm/).
+- [The Ethereum Yellow Paper](https://ethereum.github.io/yellowpaper/paper.pdf).