Back to Home

Contract 0xd9c44f093825...cbe9fb73ea24

Utility
0xd9c44f093825...cbe9fb73ea24
FrontierContract #682Source VerifiedEdit this contract
Deployed September 1, 2015 (11 years ago)Block 171,181

The 2015 ethereum.org democracy tutorial under its original name: token holders propose payments, vote a position, and the contract pays out if the vote passes.

Frontier EraVerified Source

Historical Significance

The earlier name and the earlier shape of the tutorial that later became Association, and the one that was current while The DAO was being designed. Votes are cast as a signed position rather than a boolean, weighting happens at tally time, and the founder is recorded but given no special power, which makes it a clean statement of the idea: shareholders vote, and the treasury pays out when they agree.

Context

Ethereum's Frontier network went live on 30 July 2015 and the ethereum.org tutorials followed within weeks. The democracy page was the third of them, after the token and the crowdsale, and the contract it taught was renamed and rewritten several times over the following year.

Key Facts
Deployment Block
171,181
Deployment Date
Sep 1, 2015, 04:42 AM
Code Size
3.6 KB
Gas at Deploy
1,033,134

Description

The democracy contract from the 2015 ethereum.org tutorial, in the revision that still called itself Democracy. Membership is holding a balance in a separate token: the contract stores that token's address, the account that deployed it as founder, a minimum quorum and a debating period fixed at construction.

Any holder may open a proposal naming a recipient, an amount, a word of data and a text description. Holders then vote by sending a position of minus one, zero or one, weighted later by their token balance, and each address may vote once per proposal. When the debating period has passed the proposal is tallied and, if the vote carries and the quorum is met, the contract sends the proposed amount to the recipient.

The proposal stores a single word of data rather than a hash of the transaction to be sent, so what a vote commits to is narrower than in the revisions that followed.

Heuristic Analysis

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

Detected Type: Utility

Bytecode Overview

Opcodes3,689
Unique Opcodes173
Jump Instructions134
Storage Operations97

External Links

Related contracts