> For the complete documentation index, see [llms.txt](https://blockchain-journal-hope-mabuza.gitbook.io/blockchain-journal-hope-mabuza-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blockchain-journal-hope-mabuza.gitbook.io/blockchain-journal-hope-mabuza-docs/smart-contracts/week-1-introduction-to-blockchain-history-and-architecture..md).

# Week 1 : Introduction to Blockchain, History, and Architecture.

#### Day 1 <a href="#day-1" id="day-1"></a>

**Why Blockchain Exists**

* Decentralization came about after the 2008 financial crisis exposed just how fragile centralized financial systems really are. Banks and institutions had too much control, and when they failed, ordinary people paid the price. The idea behind blockchain was to remove that single point of trust and replace it with something no one person or organization could own or control. The finance industry is one of the biggest areas that blockchain could change, and even though they are adopting it slowly and carefully, the appeal makes sense, security and immutability are hard to argue with. What stuck with me today is that blockchain wasn't just a technical invention, it was built out of frustration with a broken system.

***

#### Day 2 <a href="#day-2" id="day-2"></a>

**The Double-Spend Problem and How Consensus Solves It**

* When Satoshi Nakamoto created the decentralized form of currency, he came across a problem of double-spending. Meaning there was a risk of a single coin being spent more than once. The solution to this problem was creating an agreement process called the consensus mechanism, using cryptography to show ownership of digital assets and having a public ledger.

***

#### Day 3 <a href="#day-3" id="day-3"></a>

**How a Distributed Network Replaces a Central Authority**

* By removing a central authority, there must be a way to verify transactions, which is handled by a distributed network of participants through a consensus mechanism. Consensus ensures all participants agree on valid transactions, making the network secure and reliable.

  In traditional software, a single centralized database can be a single point of failure, if the database server goes down, the entire application becomes unavailable.

***

#### Day 4 <a href="#day-4" id="day-4"></a>

**Seeing It for Real on Etherscan**

* After setting up my MetaMask and doing a transaction, I went to look it up on Etherscan and honestly it was a bit of a cool moment. There was my wallet address, sitting on a public ledger for anyone in the world to see. I could see the block hash, the block number, and exactly who sent and received the funds. No one put it there, no admin approved it, it just exists. I think that's when the idea of trustless systems started to actually click for me, not because someone explained it better, but because I saw my own transaction and realized there's nothing to trust because there's nothing to hide.

***

#### Day 5 <a href="#day-5" id="day-5"></a>

**The Blockchain Ledger vs a Normal Database**

* The immutable blockchain ledger is different from a normal SQL database because it cannot be deleted or edited, you can view the full history of everyone's transactions. A normal SQL database has an admin, while the ledger is not owned by a single person or organisation. The part that really got me thinking was the flip side of immutability, in a regular database, a developer can just fix a mistake. On the blockchain, if you send funds to the wrong address or deploy a contract with a bug, it stays there forever. That permanence is what makes the system trustworthy, but it also means the stakes of getting things right are much higher than I was used to.

***

#### Day 6 (ABC) <a href="#day-6-abc" id="day-6-abc"></a>

**Deploying, Verifying and Bridging for the First Time**

* My first ABC meeting and it already threw me in the deep end a bit. We covered deploying and verifying smart contracts, and also how bridging works between tokens. The deployment part felt manageable, but verifying the contract on Etherscan was new to me. It makes the source code publicly readable so anyone can actually inspect what a contract does instead of just seeing a wall of bytecode. Bridging was the part that surprised me most, the idea that you can move assets between entirely different networks without going through a centralized exchange is wild when you think about how different that is from traditional finance. Lots to take in but it's starting to feel exciting rather than just overwhelming.

***