Back to Home

Delegator

0x000d96a0a3a6...95a71b87c85d
ByzantiumSource VerifiedEdit this contract
Deployed August 3, 2018 (8 years ago)Block 6,083,583

Augur's Delegator, resolving its implementation by name through the Augur controller on every call.

Byzantium EraVerified Source

Historical Significance

Augur addressed its components by name rather than by address, and every deployed piece sat behind one of these. Three separate families share this exact bytecode, differing only in the constructor arguments that set the controller and key, which is why they appear as distinct deployments of a single design.

Key Facts
Deployment Block
6,083,583
Deployment Date
Aug 3, 2018, 11:53 PM
Code Size
663.0 B
Transactions by Year
20181

Description

The contract holds a controller and a lookup key. Its fallback returns without doing anything when the key is unset, then otherwise calls lookup on the controller with that key, delegatecalls the returned address with the original calldata, and passes the return data straight back.

getController and setController come from Augur's Controlled base, with setController callable only by the current controller. controllerLookupName exposes the key, so the component a delegator stands in for can be read directly from the chain.

Source Verified

Solidityeh_crack_source_verified
Compiler: v0.4.20

Bytecode Overview

Opcodes663
Unique Opcodes105
Jump Instructions30
Storage Operations11

External Links