Back to Home

UrlHint

Utility
Linagee Name Registrar
0xe76f218ed471...25016c16e944
FrontierContract #471Source VerifiedEdit this contract
Deployed August 25, 2015 (11 years ago)Block 139,487

A registry mapping a content hash to the URL it can be fetched from, stored in 32-byte pieces, claimable by whoever registers it first.

Frontier EraVerified Source

Historical Significance

The location half of the early Ethereum content lookup. The chain can hold a hash cheaply but not a document, so tooling of the period stored the hash on chain and the URL beside it, accepting that the chain guarantees which document is meant while saying nothing about whether it can still be downloaded.

Context

Ethereum's Frontier network went live on 30 July 2015. The chain carried almost no applications in its first months: what was deployed was mostly tutorial code, token experiments and registries, written in a Solidity that was itself only a few months old and compiled from the geth console.

Contract Information
Registered Name
UrlHint
Linagee Name Registrar
An early name registry deployed by linagee on August 8, 2015 — two days before the official GlobalRegistrar. Identical bytecode. First name registered: 'MyFirstCoin' (the ethereum.org tutorial example).
Key Facts
Deployment Block
139,487
Deployment Date
Aug 25, 2015, 05:36 AM
Code Size
200.0 B
Gas at Deploy
70,687

Description

URLhint maps a 256-bit hash to a URL. Because a URL does not fit in one word, it is written in 32-byte pieces: register(hash, index, chunk) stores one piece at a time in a fixed array of 256 slots, and a reader reassembles them in order.

Ownership is first come, first served and per hash rather than per contract. Whichever account registers a hash earliest becomes the owner of that entry and is the only one who can change it afterwards, while every other hash stays open to anyone.

Paired with a hash registry, the two answer the two halves of a lookup: what document describes this thing, and where can that document be fetched from.

Heuristic Analysis

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

Detected Type: Utility

Bytecode Overview

Opcodes200
Unique Opcodes45
Jump Instructions11
Storage Operations5

External Links

Related contracts