Back to Home

Harambe(HARAMBE)

0xade6fdaba164...f234470938c6
Source VerifiedEdit this contract
Deployed February 6, 2022 (4 years ago)Block 14,155,328

Fractional ownership of a basket of five Harambe artworks, split into 100 billion ERC20 claims, with no holder having ever voted a price.

Verified Source

Historical Significance

Harambe is the case where the ownership layer and the meme layer come apart. The gorilla's death produced real public grief and then years of deliberately absurd mourning, an irony so thoroughly layered that sincerity and joke stopped being separable. A basket of five commissioned artworks, fractionalised into a token nobody has ever priced, is a fitting artefact of that.

The zero is the part worth keeping. Every other vault in this group has holders who at least went through the motions of naming a number. Here nobody did, and the contract's own rules turn that silence into a permanent lock. It is the clearest demonstration in the set that fractional.art's buyout mechanism could be defeated simply by not using it.

Token Information
Token Name
Harambe
Symbol
HARAMBE
Decimals
18
Key Facts
Deployer
nfd.eth (0x0aaef7...2b72cc)
Deployment Block
14,155,328
Deployment Date
Feb 6, 2022, 10:56 PM
Code Size
252.0 B
Transactions by Year
20221,940
2023312
2024674
2025115
202680

Description

This vault is the only one of its group that does not hold a single artwork. Its NFT is token 0 of an NFT Basket contract, and the basket in turn holds five Foundation tokens titled Harambe #002 through Harambe #006. The curator deposited them, withdrew three, and then deposited five, which the basket's transfer history records in full. Their shared description is the plain account of the gorilla: seventeen years old, resident at the Cincinnati Zoo, killed by zoo officials on 28 May 2016.

The address people hold is 252 bytes of proxy. InitializedProxy, written by Anna Carroll for fractional.art, stores one immutable address and delegatecalls everything to it: the constructor delegatecalls its initialization calldata, and the fallback forwards every later call. All of the ERC20 behaviour, and all of the buyout machinery, lives in a shared TokenVault deployed once and reused by every vault, alongside a single Settings contract that holds the platform limits.

The vault owns the artwork outright and the tokens are claims on it. Anyone may take the NFT away, but only by buying out every holder at once: reservePrice is the weighted average of the buyout prices individual holders have voted for, and start() refuses a bid below it. There is a second lock as well. Settings requires holders of at least half the supply to have voted a price before any auction can begin, so a quiet holder base is itself a veto.

Here the second lock is absolute. No holder has ever voted a price, so votingTokens is zero, reservePrice returns zero, and the quorum check can never pass. A buyout is not expensive, it is unavailable.

Source Verified

SolidityEtherscan verified
Compiler: v0.8.5+

Bytecode Overview

Opcodes252
Unique Opcodes105
Jump Instructions11
Storage Operations3

External Links