Bitcoin Network Architecture:

┌─────────────────────────────────────────────────────────────────────┐
│                         Bitcoin Network                            │
│                                                                   │
│  ┌─────────────────────────────────────────────────────────────┐   │
│  │                     Full Nodes                              │   │
│  │  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐      │   │
│  │  │   Node 1    │──│   Node 2    │──│   Node 3    │      │   │
│  │  └─────────────┘  └─────────────┘  └─────────────┘      │   │
│  │       │                │                │                  │   │
│  │  ┌────┴────┐      ┌────┴────┐      ┌────┴────┐         │   │
│  │  │ Node 4  │      │ Node 5  │      │ Node 6  │         │   │
│  │  └─────────┘      └─────────┘      └─────────┘         │   │
│  └─────────────────────────────────────────────────────────────┘   │
│                              │                                    │
│  ┌───────────────────────────▼─────────────────────────────────┐   │
│  │                      Mining Nodes                           │   │
│  │  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐       │   │
│  │  │   Miner 1   │  │   Miner 2   │  │   Miner 3   │       │   │
│  │  │  (Pool)     │  │  (Pool)     │  │  (Solo)     │       │   │
│  │  └─────────────┘  └─────────────┘  └─────────────┘       │   │
│  └─────────────────────────────────────────────────────────────┘   │
│                              │                                    │
│  ┌───────────────────────────▼─────────────────────────────────┐   │
│  │                     Light Clients                           │   │
│  │  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐       │   │
│  │  │  SPV Wallet │  │  Mobile     │  │  Web Wallet │       │   │
│  │  │             │  │  Wallet     │  │             │       │   │
│  │  └─────────────┘  └─────────────┘  └─────────────┘       │   │
│  └─────────────────────────────────────────────────────────────┘   │
└─────────────────────────────────────────────────────────────────────┘

Network Connections:
1. Full nodes connect to 8-12 peers (default)
2. Miners connect to full nodes for block propagation
3. Light clients connect to full nodes for verification
4. All communication is encrypted (optional)

Minimum Requirements (2024):
- Storage: 500+ GB (growing)
- RAM: 4+ GB (8 GB recommended)
- CPU: 2+ cores
- Network: 50+ Mbps (upload and download)
- Uptime: 24/7 recommended
- Initial Download Time: 3-7 days

Bitcoin Core Configuration:
# bitcoin.conf
txindex=1
server=1
rpcuser=bitcoinuser
rpcpassword=securepassword
maxconnections=12
dbcache=2048
datadir=/path/to/bitcoin/data

Mining Node Functions:
1. Collect pending transactions from mempool
2. Build candidate block
3. Solve PoW puzzle
4. Broadcast new block
5. Collect block reward + fees

Types of Miners:
1. Solo Miners: Mine independently
2. Mining Pools: Combine hash power
3. Cloud Miners: Rent hash power

SPV Node Architecture:

┌─────────────────────────────────────────────────────────────────────┐
│                      SPV Node Operation                            │
│                                                                   │
│  1. Download block headers (only 80 bytes each)                  │
│  2. Request Merkle proofs for transactions                       │
│  3. Verify transaction inclusion                                 │
│  4. Trust full nodes for transaction validation                  │
│                                                                   │
│  Benefits:                                                        │
│  • Low storage requirements (~100 MB)                           │
│  • Fast synchronization                                          │
│  • Mobile-friendly                                               │
│                                                                   │
│  Limitations:                                                     │
│  • Cannot validate transactions independently                   │
│  • Requires trust in full nodes                                 │
│  • Vulnerable to some attacks                                   │
└─────────────────────────────────────────────────────────────────────┘

Bitcoin Block Structure:

Block Size: Up to 4 MB (SegWit enabled)
Block Time: ~10 minutes (target)
Current Block Height: ~850,000 (as of 2024)

┌─────────────────────────────────────────────────────────────────────┐
│                          Block                                     │
│                                                                   │
│  Block Header (80 bytes):                                         │
│  ┌─────────────────────────────────────────────────────────────┐   │
│  │  Version (4 bytes): Block format version                   │   │
│  │  Previous Block Hash (32 bytes): Link to parent block      │   │
│  │  Merkle Root (32 bytes): Hash of all transactions          │   │
│  │  Timestamp (4 bytes): Unix time (seconds since 1970)      │   │
│  │  Difficulty Target (4 bytes): Current mining difficulty    │   │
│  │  Nonce (4 bytes): Proof-of-work counter                   │   │
│  └─────────────────────────────────────────────────────────────┘   │
│                                                                   │
│  Transaction Count (Variable): Number of transactions             │
│                                                                   │
│  Transaction List:                                                │
│  ┌─────────────────────────────────────────────────────────────┐   │
│  │  Tx 1: Coinbase transaction (block reward + fees)          │   │
│  │  Tx 2: Payment transaction                                 │   │
│  │  Tx 3: Payment transaction                                 │   │
│  │  ...                                                       │   │
│  │  Tx N: Payment transaction                                 │   │
│  └─────────────────────────────────────────────────────────────┘   │
└─────────────────────────────────────────────────────────────────────┘

Block Hash = SHA-256(SHA-256(Block_Header))

Where Block_Header = Version + Prev_Hash + Merkle_Root + Timestamp + Difficulty + Nonce

Example:
Block #0 (Genesis):
Header: 0x01000000 0x0000000000000000000000000000000000000000000000000000000000000000 0x3ba3edfd7a7b12b27ac72c3e67768f617fc81bc3888a51323a9fb8aa4b1e5e4a 0x4a5c1e49 0x1d00ffff 0x1dac2b7c
Hash: 0x000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f

Genesis Block Details:
- Block #0
- Nonce: 2083236893
- Difficulty: 1
- Timestamp: 1231006505 (Jan 3, 2009)
- Transactions: 1 (coinbase)
- Coinbase Message: "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks"

Meaning of Message:
1. Proof that block was created on or after Jan 3, 2009
2. Political statement (critique of traditional banking)
3. Historical marker (birth of cryptocurrency)
4. Reference to the financial crisis

UTXO Model Explanation:

UTXO = Unspent Transaction Output
Each UTXO has:
- Amount (in satoshis)
- Script (spending conditions)
- Transaction ID
- Output Index

UTXO Set = All UTXOs in the blockchain
Current UTXO Set: ~100 million UTXOs (as of 2024)

Transaction Flow:
┌─────────────────────────────────────────────────────────────────────┐
│                                                                   │
│  Inputs (Consumes UTXOs):                                         │
│  ┌─────────────────────────────────────────────────────────────┐   │
│  │  UTXO₁: 5.0 BTC (from Tx A)                               │   │
│  │  UTXO₂: 3.0 BTC (from Tx B)                               │   │
│  │  Total Input: 8.0 BTC                                     │   │
│  └─────────────────────────────────────────────────────────────┘   │
│                              │                                    │
│                              ▼                                    │
│  Outputs (Creates UTXOs):                                         │
│  ┌─────────────────────────────────────────────────────────────┐   │
│  │  Output₁: 4.0 BTC (to Recipient)                          │   │
│  │  Output₂: 3.5 BTC (change to sender)                     │   │
│  │  Total Output: 7.5 BTC                                   │   │
│  │  Transaction Fee: 0.5 BTC                                 │   │
│  └─────────────────────────────────────────────────────────────┘   │
└─────────────────────────────────────────────────────────────────────┘

UTXO Lifecycle:

Creation:
1. Transaction creates output(s)
2. UTXO added to UTXO set
3. Balance = sum of all UTXOs

Consumption:
1. Transaction uses UTXO as input
2. UTXO removed from UTXO set
3. New UTXOs created

Spent: UTXO removed from set
Unspent: UTXO remains in set

Address Generation Flow:

Private Key (256 bits)
     │
     ▼
Elliptic Curve Multiplication (secp256k1)
     │
     ▼
Public Key (33 or 65 bytes)
     │
     ▼
SHA-256 Hash (32 bytes)
     │
     ▼
RIPEMD-160 Hash (20 bytes)
     │
     ▼
Add Version Byte (0x00 = Mainnet, 0x6F = Testnet)
     │
     ▼
Double SHA-256 Checksum (4 bytes)
     │
     ▼
Base58Check Encoding
     │
     ▼
Bitcoin Address (34 characters)

Example Address: 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa

Legacy Address (P2PKH):
1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa

SegWit Address (Bech32):
bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq

Taproot Address (Bech32m):
bc1p5d7rjq7g6rdk2yhzks9smlaqtedr4dekq08ge8qt2acp

Benefits of SegWit/Taproot:
- Lower fees (smaller transaction size)
- More efficient use of block space
- Better security (future upgrades)
- Flexible spending conditions

P2PKH (Pay to Public Key Hash):
OP_DUP OP_HASH160 <pubkey_hash> OP_EQUALVERIFY OP_CHECKSIG

P2SH (Pay to Script Hash):
OP_HASH160 <script_hash> OP_EQUAL

P2PK (Pay to Public Key):
<pubkey> OP_CHECKSIG

P2WPKH (Pay to Witness Public Key Hash):
OP_0 <pubkey_hash>

P2TR (Pay to Taproot):
OP_1 <pubkey_hash>

Bitcoin Blockchain Storage:

Full Node (Archival):
- Blockchain: ~500 GB (as of 2024)
- Indexes: ~50-100 GB
- Total: ~600 GB

Pruned Node:
- Blockchain: ~2-10 GB (pruned)
- Indexes: Minimal
- Total: ~5-15 GB

SPV Node (Light Client):
- Headers only: ~100 MB
- Total: ~200 MB

Growth Rate:
- ~50-60 GB per year
- Increasing with adoption
- Pruning helps reduce requirements

Pruning Process:

1. Node downloads full blockchain
2. Validates all blocks
3. Deletes old block data
4. Keeps:
   - UTXO set
   - Block headers
   - Recent blocks

Benefits:
- Lower storage requirements
- Same validation security
- Fast synchronization

Limitations:
- Cannot serve historical data
- Cannot rescan from genesis
- Need to keep UTXO set

Peer Discovery Process:

1. DNS Seeds:
   - Hardcoded DNS names
   - Return random active node IPs
   - Example: seed.bitcoin.sipa.be

2. Hardcoded Nodes:
   - Built-in list of known nodes
   - Fallback if DNS fails

3. ADDR Messages:
   - Peers share addresses
   - Build peer list
   - Maintain connectivity

4. Peer Selection:
   - Random selection
   - Geographically diverse
   - Connect to 8-12 peers

Bitcoin Raw Transaction:

Transaction Version (4 bytes)
───────────────┬──────────────────────────────────────────────────────
               │
Input Count (Variable)
───────────────┬──────────────────────────────────────────────────────
               │
For each Input:
  Previous Transaction Hash (32 bytes)
  Output Index (4 bytes)
  Script Length (Variable)
  Script Sig (Variable)
  Sequence (4 bytes)
───────────────┬──────────────────────────────────────────────────────
               │
Output Count (Variable)
───────────────┬──────────────────────────────────────────────────────
               │
For each Output:
  Amount (8 bytes, in satoshis)
  Script Length (Variable)
  Script PK (Variable)
───────────────┬──────────────────────────────────────────────────────
               │
Locktime (4 bytes)

Serialization:
- Little-endian for integers
- Variable-length integers (CompactSize)

Fee Calculation:

Fee = Input_Amount - Output_Amount

Fee Rate = Fee / Transaction_Size

Priority:
- Higher fee rate = Faster confirmation
- Fee market determines rates
- Based on block space demand

Fee Estimation:
1. Current mempool size
2. Recent transaction fees
3. Block space availability

Recommended Fee (2024):
- Low priority: 1-2 sat/vB
- Medium priority: 2-5 sat/vB
- High priority: 5-10 sat/vB

# Concept: Bitcoin Transaction Construction

def create_bitcoin_transaction(inputs, outputs, change_address, fee_rate):
    """
    Build a Bitcoin transaction
    
    inputs: List of UTXOs to spend
    outputs: List of recipients (address, amount)
    change_address: Address for change output
    fee_rate: Fee per byte (sat/vB)
    """
    
    # Calculate total input amount
    total_input = sum(tx['amount'] for tx in inputs)
    
    # Calculate total output amount
    total_output = sum(amt for addr, amt in outputs)
    
    # Initial fee estimate
    estimated_size = estimate_tx_size(inputs, outputs)
    fee = estimated_size * fee_rate
    
    # Calculate change amount
    change = total_input - total_output - fee
    
    if change < 0:
        raise ValueError("Insufficient funds")
    
    # Add change output (if significant)
    if change > 1000:  # Skip dust outputs
        outputs.append((change_address, change))
    
    # Build transaction
    tx = {
        'version': 1,
        'inputs': inputs,
        'outputs': outputs,
        'locktime': 0
    }
    
    return tx

Bitcoin Scalability:

Block Size: 1 MB (base) / 4 MB (SegWit)
Block Time: ~10 minutes
TPS: ~7 transactions per second

Compared to Visa: ~24,000 TPS
Comparison: Bitcoin can process 0.6M transactions/day

Capacity Bottleneck:
- Network: 7 TPS
- User growth: ~50% per year
- Problem: Demand exceeds supply

Solutions:
1. On-chain scaling: Larger blocks
2. Off-chain scaling: Layer-2 (Lightning)
3. Sidechains: Separate chains
4. Optimizations: SegWit, Taproot

Lightning Network Concept:

1. Open Payment Channel:
   - Two parties lock funds in multi-sig
   - Channel balance: 1 BTC each

2. Off-chain Transactions:
   - Update channel balance
   - Transactions not on-chain
   - Instant settlement

3. Close Channel:
   - Final transaction on-chain
   - Settle final balances
   - On-chain confirmation

Benefits:
- Instant payments
- Low fees (satoshis)
- High throughput
- Privacy

Payment Channel Example:

Alice and Bob open channel:
- Alice deposits: 1 BTC
- Bob deposits: 1 BTC
- Channel capacity: 2 BTC

Alice pays Bob 0.1 BTC:
- Alice's balance: 0.9 BTC
- Bob's balance: 1.1 BTC

Alice pays Bob another 0.2 BTC:
- Alice's balance: 0.7 BTC
- Bob's balance: 1.3 BTC

Close channel:
- Final settlement: Alice 0.7 BTC, Bob 1.3 BTC
- One on-chain transaction

Routing Example:

Alice wants to pay Dave through Lightning:
- Channel Alice-Bob (capacity: 1 BTC)
- Channel Bob-Charlie (capacity: 0.5 BTC)
- Channel Charlie-Dave (capacity: 0.3 BTC)

Payment Path: Alice → Bob → Charlie → Dave

Routing Process:
1. Alice: "I want to pay Dave 0.1 BTC"
2. Network finds path
3. Funds flow through channels
4. Dave receives payment
5. All channel balances updated

Hash Time-Locked Contracts (HTLC):
- Secure routing
- Trustless transfers
- Atomic payments

Channel Opening:

1. Create Funding Transaction:
   - Multi-signature output
   - Both parties sign
   - Broadcast to network

2. Wait for Confirmations:
   - Usually 1-6 blocks
   - Finality required

3. Channel Active:
   - Off-chain transactions
   - Instant updates

4. Capacity:
   - Total funds locked
   - Available for routing

Channel Closing:

1. Mutual Close:
   - Both parties agree
   - Final transaction
   - No penalty

2. Force Close:
   - One party closes
   - Wait for dispute period
   - In case of dispute

3. Dispute Resolution:
   - Broadcast latest state
   - Penalize if cheating
   - Fair settlement

Penalty:
- If one party cheats (old state)
- All funds go to honest party
- Economic disincentive

Bitcoin Ecosystem:

1. Core Protocol:
   - Bitcoin Core (reference client)
   - Consensus rules
   - Network protocol

2. Wallets:
   - Hardware (Ledger, Trezor)
   - Software (Electrum, Bitcoin Core)
   - Mobile (BlueWallet, BRD)

3. Exchanges:
   - Centralized (Coinbase, Binance)
   - Decentralized (DEXs)

4. Mining:
   - Mining pools (Foundry, Antpool)
   - Hardware (Bitmain, MicroBT)

5. Lightning Network:
   - Nodes (LND, c-lightning)
   - Wallets (Phoenix, Breez)

6. Layer-2 Solutions:
   - Sidechains (Liquid, Rootstock)
   - State channels

Bitcoin Future Developments:

1. Scaling:
   - Lightning Network growth
   - Sidechain adoption
   - Block size optimization

2. Privacy:
   - Confidential transactions
   - CoinJoin adoption
   - Taproot privacy

3. Programmable Money:
   - Smart contracts (Taproot)
   - DLCs (Discreet Log Contracts)
   - Oracles integration

4. Institutional Adoption:
   - ETFs
   - Corporate treasuries
   - Payment integration

5. Quantum Resistance:
   - Post-quantum cryptography
   - Signature upgrades
   - Address format updates

Bitcoin Use Cases:

1. Store of Value:
   - Digital gold
   - Inflation hedge
   - Wealth preservation

2. Payments:
   - Peer-to-peer transfers
   - Cross-border payments
   - Micropayments (Lightning)

3. Financial Products:
   - Lending
   - Borrowing
   - Derivatives

4. Development:
   - Smart contracts
   - DLCs
   - Oracle integration

5. Social Impact:
   - Financial inclusion
   - Censorship resistance
   - Economic freedom

Bitcoin Economics:

1. Fixed Supply:
   - 21 million coins
   - Deflationary
   - Scarcity

2. Halving:
   - Every 210,000 blocks
   - Reward halves
   - Supply rate decreases

3. Stock-to-Flow:
   - Stock: Existing supply
   - Flow: New supply
   - Predictive of price

4. Market Capitalization:
   - Price × Supply
   - ~$1T+ (2024)
   - Leading cryptocurrency