Back to Home

OraclizeAddrResolver

Unclassified
0x3ae1631cf21f...ca8ed49b3529
FrontierContract #2,603Exact Bytecode MatchEdit this contract
Deployed October 24, 2015 (11 years ago)Block 433,213

Oraclize's second address resolver, October 2015: the fixed version, where getAddress() returns the stored Oraclize connector address.

Frontier EraVerified Source

Historical Significance

The intermediate step between Oraclize's broken first resolver and the 0x1d11e5ea resolver that its December 2015 API used. Source reconstructed from bytecode; exact runtime and creation match with solc v0.1.6, verified on Etherscan and Sourcify.

Context

Deployed on 24 October 2015 by the Oraclize operator account, 37 minutes after the first resolver at 0xda0181a763b533e532248f6ff859e564a470d9aa, whose getAddress() always returned zero.

Key Facts
Deployment Block
433,213
Deployment Date
Oct 24, 2015, 04:00 PM
Code Size
504.0 B
Gas at Deploy
159,983
Transactions by Year
20158

Description

The owner stores the current Oraclize connector with setAddr(), restricted to the deployer by a throw, and both addr() and getAddress() return it. It is the same logic as the resolver Oraclize deployed 90 minutes later at 0x1d11e5eae3112dbd44f99266872ff1d07c77dce8, but here the state variables are declared after the functions, which changes the layout of the compiled code. It still points to 0x3a0aeee3d335fc256ef70626faf66f5e43605254.

Source Verified

SolidityExact bytecode match(504 bytes)
Compiler: v0.1.6+
Heuristic Analysis

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

Detected Type: Unclassified

Bytecode Overview

Opcodes504
Unique Opcodes60
Jump Instructions16
Storage Operations8

External Links

Related contracts