Historical Significance
Controller is an early example of the contract-routing pattern: a lightweight proxy that forwards calls to a target address with access control. This pattern is ubiquitous in modern DeFi and NFT contracts but was novel in September 2015. Its role as the admin gate for Pool5x also shows early experimentation with cross-contract access control.
Context
Deployed seven weeks after Ethereum mainnet launch, during the first wave of intensive contract experimentation by the Oraclize team. Solidity v0.1.1 was the current compiler. The three-contract forwarding chain (Pool5x -> Controller -> target) foreshadows the proxy patterns that would later become standard for upgradable contracts (EIP-1967, OpenZeppelin proxies).
Key Facts
Description
Verified with soljson-v0.1.1+commit.6ff4cd6 and optimizer ON.
Source Verified
Backfilled from awesome-ethereum-proofs PR #48.
Heuristic Analysis
The following characteristics were detected through bytecode analysis and may not be accurate.
Frontier Era
The initial release of Ethereum. A bare-bones implementation for technical users.
Bytecode Overview
Verified Source Available
Source verified through compiler archaeology and exact bytecode matching.
View Verification ProofShow source code (Solidity)
contract T {
function set(uint256 x);
}
contract Controller {
T target = T(0x9e0ae8ffd946d12d1d393c6f3bca0eecadc9428e);
function set(uint256 x) {
T t = target;
t.set(x);
}
function get() returns (uint8) {
return 0xff;
}
}