Back to Home

Verify Token(VTX)

Token
0x5847610405ff...1676f1ea4afa
HomesteadDecompiledEdit this contract
Deployed June 24, 2016 (10 years ago)Block 1,763,652

A ConsenSys HumanStandardToken deployed as Verify Token, symbol VTX, with 3 decimals and a fixed supply credited to its deployer.

Homestead Era

Historical Significance

The ConsenSys token contracts were what a developer copied between the ethereum.org tutorials and OpenZeppelin, and the human-readable variant is the one that fixed the convention every wallet now relies on: a name, a symbol and a decimals value living on the token itself rather than in a list somebody maintains. The version string it carries, H0.1, identifies the implementation as much as the token.

Context

Deployed in mid 2016, after Homestead and after ERC-20 had settled the interface but before OpenZeppelin existed. The ConsenSys Tokens repository was the reference implementation of the period, and its choices, a boolean return from transfer, an allowance mapping and a supply fixed at construction, are visible in the deployments that copied it.

Token Information
Token Name
Verify Token
Symbol
VTX
Decimals
3
Key Facts
Deployment Block
1,763,652
Deployment Date
Jun 24, 2016, 04:00 PM
Code Size
1.8 KB

Description

A ConsenSys HumanStandardToken: the ERC-20 interface with the human-readable fields the standard left optional, name, symbol and decimals, plus a version string. Balances live in a public mapping, transfer and transferFrom check the sender's balance and the recipient's for overflow, approve writes an allowance, and both Transfer and Approval events are emitted.

The whole supply is credited to the deployer at construction. There is no owner, no minting and no freezing, so nothing about the token can change after the transaction that created it.

This one was deployed as Verify Token with the symbol VTX and 3 decimal places, and an opening supply of 10,000 base units. It reports its implementation version as H0.1.

Heuristic Analysis

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

Detected Type: Token

Bytecode Overview

Opcodes1,804
Unique Opcodes150
Jump Instructions81
Storage Operations33

External Links

Related contracts