Back to Home

Contract 0x1e6fe309757a...24f94266c214

Utility
0x1e6fe309757a...24f94266c214
FrontierContract #832Source VerifiedEdit this contract
Deployed September 5, 2015 (10 years ago)Block 186,501

The ethereum.org crowdsale tutorial: contributions run to a deadline against a goal, pay out a separate reward token, and are refunded if the goal is missed.

Frontier EraVerified Source

Historical Significance

This is what a token sale looked like before ERC-20 existed: a fixed price, a deadline, a threshold, an automatic refund if the threshold is missed, and the tokens themselves held in a separate contract addressed through sendCoin rather than transfer. The all-or-nothing goal it implements is the pattern token sales kept using for years after this code was replaced.

Context

Ethereum's Frontier network went live on 30 July 2015 and the ethereum.org tutorials were the main worked examples anyone had. This crowdsale predates ERC-20, which is why the token it pays out is addressed through sendCoin and coinBalanceOf rather than transfer and balanceOf.

Key Facts
Deployment Block
186,501
Deployment Date
Sep 5, 2015, 03:43 AM
Code Size
2.2 KB
Gas at Deploy
665,240

Description

A crowdfunding contract from the 2015 ethereum.org tutorial. Its constructor fixes five things that can never be changed afterwards: who receives the money, the funding goal, how many minutes the campaign runs, the price of one reward token, and the address of the token contract that pays contributors.

Contributions arrive through the fallback function. Each sender is appended to a public funders array along with the amount, the running total goes up, and the reward token is asked to send that contributor the amount divided by the price. Once the deadline has passed 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 each one in turn. Either way it then self-destructs to the beneficiary.

The reward tokens have to be sitting in this contract before the sale opens and nothing here checks that they are. The refund loop is unbounded, so a campaign with enough contributors cannot be closed inside a block's gas limit, and neither the refunds nor the payout check whether send() succeeded.

It was deployed with no constructor arguments at all, so its beneficiary, funding goal, price and reward token address are every one of them zero and its deadline is the moment of deployment. Nothing could be raised through it and nothing could be paid out by it.

Heuristic Analysis

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

Detected Type: Utility
Contains SELFDESTRUCT opcode

Bytecode Overview

Opcodes2,244
Unique Opcodes139
Jump Instructions61
Storage Operations47

External Links

Related contracts