Back to Home

Congress

DAO / Governance
Part of The Avsa Collection
0x66c5bc476329...9977094e30bb
FrontierContract #8,364Exact Bytecode MatchEdit this contract
Deployed February 11, 2016 (10 years ago)Block 988,722

One of the Congress DAOs Alex Van de Sande deployed on 11 February 2016, the version that sells unicorns.

Frontier EraVerified Source

Historical Significance

The source is that verified file with transferOwnership declared inside Congress instead of inherited, and with the functions in a different order. Neither is a matter of taste. Solidity emits an inherited function ahead of the deriving contract's own, and this deployment writes the owner slot 4544 bytes in, well after code that an inherited function would have preceded. Declaration order steers the 2015 and 2016 optimizer's block layout, so the order is a reading of the deployed bytecode rather than a guess. Compiled with v0.2.0-nightly.2016.1.13+commit.d2f18c73 with the optimizer on, it reproduces all 7189 bytes of the deployment transaction exactly.

Context

Deployed on 11 February 2016, one of a run of Congress and token contracts this account put on chain that day while the DAO tutorial was being reworked. Another Congress went out from the same account the same day, at 0xfb6916095ca1df60bb79ce92ce3ea74c37c5d359, and was verified on Etherscan at the time. It is the same contract with its functions written in a different order.

Key Facts
Deployment Block
988,722
Deployment Date
Feb 11, 2016, 05:13 PM
Code Size
7.0 KB
Gas at Deploy
1,864,511

Description

Congress is the voting organisation from the ethereum.org DAO tutorial, in the form it reached by February 2016. Members carry a numeric vote weight rather than a yes or no right to vote, and a separate flag for whether they may open proposals. Proposals come in two flavours, one denominated in wei and one in ether, and each names a recipient, an amount and a payload to run. Votes are weighted by the member's weight, and once the debating period has run out executeProposal checks the quorum and the margin before sending the ether and running the payload. The contract also has a fallback function that sells unicorns: ether sent to it above the unicorn price mints unicorn tokens back to the sender through a separate token contract. It was deployed with every constructor parameter set to zero.

Source Verified

Exact bytecode match(7,189 bytes)
Compiler: v0.2.0-
Heuristic Analysis

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

Detected Type: DAO / Governance

Bytecode Overview

Opcodes7,189
Unique Opcodes226
Jump Instructions301
Storage Operations278

External Links

Related contracts