Back to Home

Contract 0xd4eae4ae8565...941d98a2c77a

Utility
0xd4eae4ae8565...941d98a2c77a
FrontierContract #55DecompiledEdit this contract
Deployed August 8, 2015 (11 years ago)Block 54,642

The ethereum.org crowdsale tutorial, deployed on the ninth day of the public chain, with the funding goal, deadline and price fixed at construction.

Frontier Era

Historical Significance

A crowdfunding contract from the first fortnight of Ethereum's public chain, running the pattern token sales used for years afterwards: a deadline, a threshold, a fixed price and an automatic refund if the threshold is missed. Its bytecode also records something about how the earliest contracts were built, since it was compiled by a build of the compiler that never shipped, which is why the source cannot be reproduced today.

Context

Ethereum's Frontier network went live on 30 July 2015 and this went on chain nine days later, when the ethereum.org tutorials were most of what existed to copy. Compilers were being cut from the development branch faster than they were released, so a contract from these weeks can carry code no published compiler produces.

Key Facts
Deployment Block
54,642
Deployment Date
Aug 8, 2015, 06:12 PM
Code Size
2.3 KB
Gas at Deploy
676,292

Description

A crowdfunding contract from the 2015 ethereum.org tutorial. It answers beneficiary(), fundingGoal(), deadline(), price() and tokenReward(), all set once at construction, keeps a running amountRaised() and a public funders array, and takes contributions through its fallback function, paying each contributor in a separate reward token at the fixed price.

After the deadline anyone may call checkGoalReached(). If the total met the goal the balance goes to the beneficiary; otherwise the contract walks the funders array and refunds them.

The Solidity source behind it has not been recovered. The deployed code accesses every member of a stored Funder through a two-instruction sequence that keeps a byte offset alongside the slot, and no released compiler of the period emits that, so the account that deployed it was building with a development build that was never published.

Heuristic Analysis

The following characteristics were detected through bytecode analysis and may not be accurate.

Detected Type: Utility
Contains SELFDESTRUCT opcode

Bytecode Overview

Opcodes2,403
Unique Opcodes145
Jump Instructions63
Storage Operations53

External Links

Related contracts