Back to Home

usingOraclize

Token
0xdde80fd813f4...e31e3d4323e4
FrontierContract #4,583Exact Bytecode MatchEdit this contract
Deployed December 5, 2015 (10 years ago)Block 647,132

The usingOraclize base contract deployed on its own, with none of the application that normally inherits it.

Frontier EraVerified Source

Historical Significance

The ethereum.org token tutorial is where most people who deployed a token in this period started, and this is its opening form: a balance mapping, a guarded subtraction and the metadata a wallet needs to show a name. It has no allowance, so nothing can spend on a holder's behalf and no exchange or escrow can be given a limit. That gap is exactly what ERC-20 was written to close, and copies like this one are the before picture.

Context

Deployed 5 December 2015, during the Frontier era.

Key Facts
Deployment Block
647,132
Deployment Date
Dec 5, 2015, 11:02 PM
Code Size
290.0 B
Gas at Deploy
90,913

Description

usingOraclize is the base contract from oraclize/ethereum-api that applications inherit to reach the Oraclize service: it holds the address resolver 0x1d11e5eae3112dbd44f99266872ff1d07c77dce8, looks the current Oraclize contract up through it before every call, and wraps oraclize_query in eight overloads plus oraclize_cbAddress, oraclize_setProof and oraclize_setNetwork. Every one of those is internal, so none of them appears in this deployment's dispatcher; what is left onchain is the parts of the base that are externally reachable and the storage slot the resolver lookup writes. The deployer put the library up by itself rather than inheriting it, so nothing calls into it.

Source Verified

Exact bytecode match(290 bytes)
Compiler: v0.1.6+
Heuristic Analysis

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

Detected Type: Token

Bytecode Overview

Opcodes290
Unique Opcodes76
Jump Instructions8
Storage Operations2

External Links

Related contracts