Skip to main content
Other Assets

Ethereum and Smart Contracts

Pomegra Learn

Ethereum and Smart Contracts

Bitcoin proved that a decentralized network could maintain a ledger without a central authority. Ethereum went further: it asked whether that same network could execute arbitrary programs. The answer was smart contracts—self-executing agreements encoded in software, running on thousands of machines simultaneously with no single operator controlling them.

This architectural shift unlocked everything built on Ethereum: decentralized finance, NFTs, prediction markets, identity systems, and thousands of experimental protocols. But it also introduced new risks. Bitcoin's security rests on relatively simple cryptography; Ethereum's rests on the correctness of complex, evolving code. When a smart contract has a bug, there's no customer service to call and no "undo" button—only the permanent ledger and the losses it records.

This chapter teaches you how Ethereum works from the ground up. You'll understand the execution environment that lets code run trustlessly, the gas pricing system that prevents abuse, and the token standards (ERC-20 for fungible tokens, ERC-721 for unique assets, ERC-1155 for hybrid models) that organize most on-chain activity. You'll learn why Ethereum migrated from proof of work to proof of stake in 2022, what "the Merge" was, and how validators replaced miners. You'll see how oracle networks like Chainlink bring off-chain data into smart contracts, and how the Ethereum Name Service lets you replace hex addresses with human-readable names.

Why this matters​

Ethereum is not just a cryptocurrency; it's a computing platform. Treating it as mere "digital money" misses the point entirely. What matters is that Ethereum lets strangers execute code together without trusting a company or government to run the servers. That capability enabled an entirely new financial ecosystem—and it also enabled new categories of fraud and collapse. Understanding the technical foundations helps you distinguish between genuine innovation and engineered scams.

What you'll learn​

This chapter starts with Ethereum's account model and how state is organized across the network. You'll study the Solidity programming language through real examples—not to become a developer, but to read and reason about the contracts you're trusting. Gas mechanics are central: why every operation costs something, how that cost is calculated, and why gas fees spike during network congestion. You'll examine the major token standards and understand why ERC-20 is the template for most new coins, how ERC-721 made NFTs possible, and why ERC-1155 emerged as a more flexible alternative. We'll walk through the consensus mechanism shift from proof of work to proof of stake, the technical details of the Merge, and how validators now secure the network. Finally, you'll see how oracles work and why they're necessary—but also why oracle reliance reintroduces trust assumptions into supposedly trustless systems.

How to read this chapter​

If you're not a programmer, the Solidity section might feel abstract at first. Read it anyway. You don't need to write contracts; you need to read them well enough to spot red flags. Start with simple ERC-20 examples, then move to more complex patterns. The gas and consensus sections are foundational; don't skip them. By the time you reach oracles and ENS, you'll have built intuition for how permissionless systems handle real-world constraints and compromises.

Understanding Ethereum is understanding the closest thing we have to a global, permissionless computer. Its limitations are profound—slow, expensive, and complex compared to traditional systems. But those limitations are the price of something unusual: code that runs anywhere, on anyone's machine, with no corporation or government capable of stopping it. That's the foundation of everything covered in subsequent chapters.

Articles in this chapter​