ICO prelude

Tokens light the fuse

Before ERC-20: experiments and promises

Bitcoin’s script was too limited for rich tokens, so early attempts happened off to the side. Mastercoin (later Omni) in 2013 layered tokens on top of Bitcoin; Counterparty followed in 2014. Both sold native tokens (MSC, XCP) to fund development, setting a pattern: whitepaper, crowdsale, promise of future utility.

Ethereum’s own 2014 presale used a Bitcoin address; buyers received ETH after genesis. It validated the idea that code-in-progress could be financed by selling future network assets. Regulators hadn’t weighed in yet; the vibe was “software presale,” not registered offering.

Ethereum makes tokens easy

Once Ethereum launched, anyone could write a token contract. Early projects hacked together custom interfaces—painful for wallets and exchanges. But the low barrier attracted builders and opportunists: raise ETH, promise a platform, ship later.

Narratives take shape

Tokens promised access to decentralized storage, compute, messaging, and games. Many were vapor; some were earnest. Investors began valuing upside via token supply and “platform potential,” not equity. This mental shift—protocol ownership via tokens—primed the 2017 surge.

Standards, tools, and hype

ERC-20 standardizes the interface

Fabian Vogelsteller proposed ERC-20 in late 2015; by 2016, it became the de facto token standard: `balanceOf`, `transfer`, `approve`, and `transferFrom`. With a common ABI, wallets could display any ERC-20, and exchanges could list them with less custom code. Interoperability poured gasoline on token launches. The original proposal lives on the EIP site ↗.

Tooling lowers the bar

Truffle added migrations and tests; OpenZeppelin published crowdsale and token libraries; tutorials showed copy-paste ICO contracts. Solidity still had footguns (no overflow checks yet), but templates reduced friction. Launching a sale shifted from bespoke work to configuration. OpenZeppelin’s early v1 contracts ↗ are a time capsule.

Marketing and FOMO

Telegram groups, Slack channels, and slick PDFs started appearing. Projects promised “utility tokens” for future networks. “Community” often meant airdrops and bounty campaigns. The ease of issuing tokens mixed with a rising ETH price to create a feedback loop: more funding, more launches.

Why this prelude mattered

Regulatory clouds

Lawyers warned that many tokens looked like securities: funds raised on future efforts. Teams leaned on “utility” language and geofenced U.S. buyers. Exchanges worried about listing risk. This gray zone set the stage for the SEC’s 2017 DAO Report and later enforcement.

Technical debt and standards

ERC-20’s simplicity had trade-offs: the missing `safeTransfer`, approval race conditions, and lack of supply metadata caused pain. These gaps led to later standards (ERC-223, ERC-777) and patterns like `safeApprove`. The prelude’s rough edges informed safer defaults.

Cultural inflection

The pre-2017 sales shifted crypto culture from “build a chain” to “build on a chain.” It blurred lines between users and investors. It also sparked skepticism: if anyone can print a token, how do you judge value? That skepticism fueled the “DYOR” ethos and the rise of audits and code reviews as table stakes.

Launchpad for the boom

By mid-2016, the ingredients were ready: a token standard, templates, rising ETH prices, and hungry investors. The ICO supercycle of 2017 was less a surprise than an acceleration of trends seeded here. DeFi and NFTs later reused the same plumbing. Understanding the prelude explains why the boom felt inevitable once the fuse was lit.