Back to Home

0x8593...27ce

DAO / Governance
Part of The Avsa Collection
0x85935ee57733...3eb5831827ce
FrontierContract #7,410Exact Bytecode MatchEdit this contract
Deployed January 29, 2016 (10 years ago)Block 923,647

A Congress DAO with separate voting and proposing rights, deployed by Alex Van de Sande on 29 January 2016.

Frontier EraVerified Source

Historical Significance

The source is the tutorial revision of 28 December 2015 with four changes, every one of them forced by the deployed bytecode: the owner renamed to administrator, the second permission flag added to the member record and to changeMembership, the proposal guard reading that new flag while the voting guard keeps reading the old one, and the quorum test tightened from less than or equal to strictly less than. Compiled with v0.1.7+commit.b4e666cc with the optimizer on, it reproduces all 5489 bytes of the deployment transaction exactly, constructor arguments included.

Context

Deployed on 29 January 2016, a month after the DAO tutorial page went up and about two weeks before the run of Congress and token deployments this account made on 11 February 2016. The two permission flags and the administrator naming are both steps toward the later version, which replaced the plain canVote flag with a numeric vote weight.

Key Facts
Deployment Block
923,647
Deployment Date
Jan 29, 2016, 06:34 PM
Code Size
5.4 KB
Gas at Deploy
1,417,662
Transactions by Year
20168

Description

Congress is the voting organisation from the ethereum.org DAO tutorial. This deployment splits membership into two permissions rather than one: each member record carries a canVote flag and a canAddProposals flag, and the two are enforced separately. Putting up a proposal requires canAddProposals, voting on one requires canVote, and the owner sets both when adding or updating a member. The owner is called the administrator here rather than the owner. A proposal names a recipient, an amount of ether and a payload; once the debating period has run out anyone can call executeProposal, which requires that the vote count reached the quorum and that the margin favours the proposal before sending the ether and running the payload. It was configured with a quorum of one, a debating period of five minutes and a majority margin of zero.

Source Verified

SolidityExact bytecode match(5,489 bytes)
Compiler: v0.1.7+
Heuristic Analysis

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

Detected Type: DAO / Governance

Bytecode Overview

Opcodes5,489
Unique Opcodes215
Jump Instructions226
Storage Operations181

External Links

Related contracts