My Web3 Journey

[femisamj]

My personal learning documentation for MGS Web3 Cohort 3!

[femisamj]

submissions/SamuelJoseph/week-1/day-2/SamuelJoseph_Blockchain_Infrastructure_Assignment.md

[femisamj]

Blockchain comparison

Blockchain	Node types	Clients / software	Consensus
Bitcoin	Full nodes, light nodes, miners	Bitcoin Core	Proof of Work (PoW). 20
Ethereum	Execution clients + Consensus clients, full/light nodes	Geth, Nethermind; Lighthouse, Prysm, Teku	Proof of Stake (PoS) (post-Merge). 21
Solana	Validators, RPC nodes, archival nodes	solana-validator (CLI)	Proof of History (PoH) + PoS (for validator selection). 22
Polkadot	Validators, nominators, collators	polkadot (Substrate clients)	Nominated Proof of Stake (NPoS). 23
Avalanche	Validators, full nodes, RPC nodes	AvalancheGo	Avalanche consensus (sub-sampled voting, fast finality). 24

[femisamj]

Distributed ledger vs Blockchain

Feature	Distributed Ledger (DLT)	Blockchain
Definition	Replicated ledger across nodes; can be permissioned	Type of DLT that stores data in cryptographically chained blocks. 25
Structure	Flexible (not necessarily block-based)	Block-chained structure
Consensus	Many types (permissioned algorithms common)	PoW/PoS/NPoS/others
Use cases	Enterprise, private networks (Hyperledger, Corda)	Public networks, open value transfer (Bitcoin/Ethereum) 26

[femisamj]

Twitter thread (7 tweet)

1. 🧵 Let’s unpack blockchain infrastructure, distributed ledgers, and how NFTs & tokens change ownership. Quick thread for #Web3 learners. #Blockchain #NFTs

2. 🔹 Blockchains differ a lot. Bitcoin (PoW) secures value, Ethereum now uses PoS with split execution/consensus clients, Solana uses PoH+PoS for speed, Polkadot uses NPoS for cross-chain governance, Avalanche uses sub-sampled voting for fast finality. Sources: official docs.

3. 🔸 Nodes & clients: running a node can be “full”, “light”, or a validator. Ethereum post-Merge needs execution + consensus clients (e.g., Geth + Lighthouse). Running nodes is how decentralization is enforced.

4. 🔁 Distributed ledger ≠ blockchain. All blockchains are DLTs, but DLTs can be blockless and permissioned (e.g., Hyperledger, Corda) — important for enterprise use cases.

5. 🖼️ NFTs vs tokens: NFTs (ERC-721/1155) are unique tokens that record provenance & ownership on-chain; fungible tokens (ERC-20) are interchangeable units used for money, utility, or governance. Standards matter.

6. 🔍 Real examples: BAYC (Ethereum NFTs), Axie (Ronin/game chain), NBA Top Shot (Flow), Royal (music royalties), USDT/USDC (stablecoins), UNI (governance token). Each shows different ownership/economic models.

7. 🧾 Ownership nuance: on-chain ownership = provable control of a token, but off-chain rights (copyright, venue access, physical item titles) depend on terms & law. Always check terms & custody. #NFTs #Law #Web3.

[femisamj]

Sources (12–15)

1. Bitcoin — Running a full node / Bitcoin Core.

2. How to run a Bitcoin node (requirements explainer).

3. Ethereum docs — execution & consensus client split (Nethermind).

4. Ethereum RPC / QuickNode / PoS references.

5. Solana — confirmation & whitepaper (Proof of History).

6. Polkadot — Nominated Proof of Stake docs.

7. Avalanche — Avalanche consensus & nodes (AvalancheGo).

8. Distributed ledger vs blockchain / Hyperledger & Corda comparisons.

9. ERC-721 standard (EIP-721 / ethereum.org).

10. ERC-20 standard (EIP-20 / ethereum.org).

11. Bored Ape Yacht Club (OpenSea collection / BAYC).

12. Axie Infinity / Ronin docs.

13. NBA Top Shot / Flow (Dapper Labs docs).

14. Royal (music NFT platform) / Alchemy case study.

15. Tether (USDT) & Circle (USDC) official pages (stablecoins).

[femisamj]

Summary of Learning – Week 1 Day 2

This assignment deepened my understanding of blockchain infrastructure.
I explored how different chains (Bitcoin, Ethereum, Solana, Polkadot, Avalanche) vary in consensus, node roles, and scalability.
I learned the difference between distributed ledgers and blockchains, and how NFTs redefine ownership through digital provenance.
I also practiced using Markdown, tables, and GitHub submission workflows.