Frontier launched Ethereum as a warned, unfinished network

Inherited archive entry · retained from the earlier edition. Its factual, legal and policy claims have not all been reverified for 19 September 2026. Research scope.

A genesis block with a warning label

Ethereum's Frontier release went live on 30 July 2015, when the network's genesis block was generated. The launch post frames the moment expansively, describing a 'censorship-proof “world computer” that anyone can program, paying exclusively for what they use and nothing more.' Eight days earlier, a companion post titled Frontier Is Coming had set a narrower expectation, calling the release 'a live, but barebone implementation' aimed at 'technical users, specifically developers' rather than the public the launch-day language addressed. Read together, the two posts describe the same event from different distances: one as an inauguration, the other as a controlled experiment.

A gas limit designed to keep the network quiet

The preparation post specifies that Frontier would launch with a hardcoded gas limit of 5,000 per block, low enough that ordinary transactions could not clear. After three to four days, an update was expected to raise the limit to 3 million gas, at which point normal activity could begin. This was a deliberate thawing period, not a bug: it gave operators time to confirm the network was behaving correctly before allowing the transaction volume a much higher limit would permit. The same post warned outright that 'there will be bugs' and told prospective users they were 'taking their chances when using the software,' promising 'big (BIG) warning messages' before installation.

Canary contracts and what caution signals

The team also deployed what the preparation post calls canary contracts, monitoring mechanisms intended to halt mining if the network showed signs of a consensus break, rather than let a divided chain run undetected. That is a materially different posture from the launch-day description of a computer 'anyone can program.' A network that ships with a deliberate stop switch for its own miners is declaring, in its own design, that its rules might fail in ways developers cannot yet predict. The gap between the two posts is not a contradiction; it is normal practice for an experimental release, but only for a reader who sees both documents rather than the more quotable one.

• Which of a project's own announcements carries the operative caveats, the celebratory one or the technical one, and has a reader seen both?
• Is a described resource limit a permanent design choice or a temporary safety throttle awaiting a scheduled increase?
• What automatic stop mechanism, if any, exists if the network's consensus breaks, and who controls it?

Frontier's first days were bounded deliberately, by a gas ceiling and by contracts built to stop mining rather than let a fault run unchecked. The launch was real. So were the caveats published alongside it, and they are the part later retellings most often drop.