Back to Home

Unicorns(w๐Ÿฆ„)

Token
0x38a9af1bd00f...8d6d3d5dca00
Source VerifiedEdit this contract
Deployed November 10, 2025 (9 months ago)Block 23,769,877

A 2025 wrapper for the Ethereum Foundation's 2016 Unicorn token, whose transfer function returns nothing and so breaks strict ERC-20 callers.

Verified Source

Historical Significance

This is the missing-return-value defect that later became famous through USDT, appearing here in a token from early 2016. It is the reason SafeERC20 and similar wrappers exist across the whole ecosystem. Unicorns shows the problem in its original habitat: a contract written when the standard was months old and the convention of returning a bool from transfer had not yet hardened into something every caller depends on.

Context

The Unicorn token dates to February 2016, when the Ethereum Foundation ran a donation drive and issued a Unicorn for each contribution to the tip jar. ERC-20 had been proposed the previous November and was still being interpreted differently by different authors. Tokens from this window are frequently correct in shape and wrong in detail, and a single missing return value is enough to put one out of reach of contracts written a few years later.

Token Information
Token Name
Unicorns
Symbol
w๐Ÿฆ„
Decimals
0
Key Facts
Deployment Block
23,769,877
Deployment Date
Nov 10, 2025, 03:53 PM
Code Size
2.6 KB
Transactions by Year
20254
20261

Description

Wrapped Unicorns (w๐Ÿฆ„) was deployed on 10 November 2025 and wraps the Unicorns token from 11 February 2016, the token the Ethereum Foundation issued in exchange for donations to its tip jar. Its verified source references the original address directly, and it keeps the original's zero decimals.

Unicorns is an unusual case among the contracts wrapped here because it is nearly compliant. It has approve, transferFrom and allowance, so at a glance it looks like an ordinary ERC-20. The defect is in the signature rather than the set of functions: transfer(address,uint256) returns nothing at all, where the standard requires it to return a bool. Any contract holding a strict IERC20 interface decodes the empty return as a failure and reverts.

The original also carries freezeAccount and frozenAccount, letting its owner freeze balances, which is behaviour no modern venue assumes. The wrapper offers wrap and unwrap and issues a fully compliant token in its place.

Historian Categories

TokenNFT / Collectible
Heuristic Analysis

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

Detected Type: Token

Bytecode Overview

Opcodes2,612
Unique Opcodes217
Jump Instructions152
Storage Operations30

External Links

Related contracts