Back to Home

Asteroid(ROID)

Token
0xd86e372a09d6...2cb610474375
ByzantiumContract #129KExact Bytecode MatchEdit this contract
Deployed October 24, 2017 (8 years ago)Block 4,419,618

ERC20 token built on OpenZeppelin v1.3.0 with owner-restricted burn function. Deployed during the 2017-2018 ICO era.

Byzantium EraVerified Source

Historical Significance

Representative of the wave of ICO-era ERC20 tokens launched in 2017 using OpenZeppelin as the de facto standard library. At the time, OZ v1.3.0 was the prevalent version for Solidity 0.4.x tokens. The pattern of inheriting StandardToken + BurnableToken + Ownable became nearly universal, appearing in hundreds of token contracts from this period. The owner-restricted burn() is a common customization that appears in many ICO tokens — project teams wanted the ability to burn unsold tokens after their sale while preventing holders from reducing circulating supply.

Context

Uses OpenZeppelin zeppelin-solidity v1.3.0 (distinct from v1.4.0 in several subtle ways: SafeMath.mul uses assert(a==0 || c/a==b) without the early-return optimization; BasicToken.transfer lacks the explicit balance check; StandardToken.allowed is not marked internal; functions use 'constant' instead of 'view'). Compiled with Solidity 0.4.13 or 0.4.15 and optimizer ON — the <=0.4.15 CALLDATASIZE ISZERO dispatch pattern confirms this. Deployed via Truffle (confirmed by the Migrations setCompleted() call in the creation transaction).

Token Information
Token Name
Asteroid
Symbol
ROID
Decimals
18
Key Facts
Deployment Block
4,419,618
Deployment Date
Oct 24, 2017, 08:32 AM
Code Size
2.8 KB
Gas at Deploy
871,463
Transactions by Year
20171

Description

AsteroidToken (ROID) is an ERC20 token built on OpenZeppelin v1.3.0, deployed in October 2017 during the peak of the ICO era. It implements StandardToken, BurnableToken, and Ownable from OpenZeppelin, with one notable customization: the burn() function is overridden to require the onlyOwner modifier, restricting token burning to the contract owner rather than allowing any holder to burn their own tokens.

The token was deployed by 0xC6218283f2b5d2c4ff3f13d2da16231a3c058bee and initialized with 10,000,000 ROID tokens (18 decimals) allocated entirely to the deployer.

Functions include the standard ERC20 set (transfer, transferFrom, approve, allowance, increaseApproval, decreaseApproval) plus burn() (owner only) and transferOwnership().

Source Verified

SolidityExact bytecode match(2,818 bytes)
Compiler: v0.4.15

Code match (executable bytecode identical, CBOR metadata hash differs — expected for reconstructed source). Compiler: solc v0.4.15+commit.8b45bddb, optimizer ON (200 runs). Built on OpenZeppelin v1.3.0. Key finding: burn() overridden with onlyOwner modifier.

Heuristic Analysis

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

Detected Type: Token
Has ERC-20-like patterns

Bytecode Overview

Opcodes2,818
Unique Opcodes201
Jump Instructions129
Storage Operations36

External Links