Back to Home

Peperium Series 2(PEPE)

Token
0x5921f43985a0...e09b96de943e
Spurious DragonContract #112KSource VerifiedEdit this contract
Deployed August 27, 2017 (8 years ago)Block 4,210,431

RARE Pepe collectible card token (Series 2). Factory-deployed by the Peperium platform with transfer events and an admin toggle.

Spurious Dragon EraVerified Source

Historical Significance

Early collectible token platform that predated ERC-721. Represents the bridge between Counterparty-era RARE Pepes and Ethereum-native digital collectibles.

Context

Peperium launched in 2017 as part of the RARE Pepe movement, which brought collectible digital art to Ethereum. Each card was its own token contract, predating the ERC-721 NFT standard. The factory pattern allowed rapid deployment of new cards while sharing identical logic.

Token Information
Token Name
Peperium Series 2
Symbol
PEPE
Decimals
0
Key Facts
Deployment Block
4,210,431
Deployment Date
Aug 27, 2017, 07:51 PM
Code Size
5.9 KB
Gas at Deploy
1,547,491
Transactions by Year
20173

Description

Peperium Series 2 card token, part of the RARE Pepe digital collectible ecosystem on Ethereum. Each card was deployed as an independent ERC-20-like contract through a factory at 0xb4e34890. The token includes standard transfer, approve, and approveAndCall functionality, plus owner-controlled minting (mintToken), account freezing (freezeAccount), and buy/sell with ETH pricing.

Series 2 added Transfer event emission to the transfer() function (missing in Series 1) and introduced a boolean admin toggle. 13 identical token contracts were deployed from this factory.

The source has been recovered to near-exact match. One unknown remains: a bool variable name (getter 0xea76f7d8, setter 0x8675c3e8) that exists in no known signature database and was never called on-chain.

Source Verified

SolidityNear-exact bytecode match
Compiler: 0.4.14+

All 21 functions, storage layout, events verified. One unknown bool variable name (getter 0xea76f7d8). Compiler: solc 0.4.14+commit.c2215d46, no optimizer.

Heuristic Analysis

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

Detected Type: Token

Bytecode Overview

Opcodes6,075
Unique Opcodes199
Jump Instructions243
Storage Operations82

External Links