EIP-8066 Upgrade mascot (Upgrade Mascots)

No call decision · Other · EIP status Last Call · created 2025-10-29

An Informational EIP that formalizes the community process for choosing a cute animal mascot for each Ethereum network upgrade. It does not change the protocol itself.

Why it is needed

Ethereum regularly ships network upgrades, but most of their content consists of complex technical changes that can feel abstract to the broader community. This EIP proposes attaching a fun, memorable mascot to each upgrade to celebrate it and draw community engagement and interest. The mascot becomes creative material for upgrade event branding such as watch parties or attendance NFTs, and builds a lighthearted Ethereum-specific tradition that sets it apart from other ecosystems. Until now there has been no official process for choosing a mascot, which risked it being decided arbitrarily on an ad hoc basis or not happening at all; this document formalizes mascot selection, already part of current practice, into a formal process.

What changes

Today

After EIP-8066

Who is affected

In depth

The four mascot requirements

Relevance: The mascot MUST be thematically related to one or more of the following: the headliner of that upgrade, the origin of the upgrade layer's name (e.g., a city for the execution layer, a star for the consensus layer), or a client interop event. Representation: It MUST be representable by one or more standard Unicode emoji. The original text cites the panda emoji for the Merge as an example. Form: It SHOULD be an animal, whether real, mythical, or stylized. Tone: It MUST NOT depict violence, discrimination, or controversy, and SHOULD be inherently cute in nature. Offensive or scary traits are avoided unless refined to be cute.

The role of the Mascot Wrestler and its two layers of veto

The Mascot Wrestler is a self-volunteered community facilitator responsible for proposing, selecting, and adopting the upgrade mascot. Specific duties include recruiting and curating candidates, running the selection process, and announcing the final mascot (on Ethereum Magicians, All Core Devs, etc.). To encourage diverse participation, the role MAY rotate voluntarily each upgrade cycle. There are two layers of veto. First, the Mascot Wrestler MAY reject candidates that fail to meet the requirements. Second, rough consensus among client teams MAY reject the selected mascot, in which case the process moves to the next-ranked candidate.

Minimum requirements for the selection process

The Mascot Wrestler SHALL run the selection in one or more ways suited to the community. The process MUST: run for at least 7 days, present 2 or more candidates, rank the final candidates by popularity, and publicly document the results. If consensus is not reached, the Mascot Wrestler selects the top-ranked candidate by default, and this choice is also subject to veto.

Usage guidelines: no memecoin promotion

All uses MUST respect the mascot's cute, non-aggressive character and, where applicable, credit the original concept creator. Mascots exist to celebrate network upgrades and SHOULD NOT be used to promote speculative tokens such as memecoins.

Design rationale and alternatives considered

This specification balances creativity with guardrails to prevent mascot drift into choices unrelated to the upgrade or into extreme territory. Emoji-based representation ensures accessibility across digital platforms, and the animal and cuteness requirements align with the approachable spirit of the Ethereum community. The volunteer-based Mascot Wrestler role decentralizes coordination while the veto ensures accountability. Three alternatives were considered and discarded: full on-chain enforcement was deemed too rigid for the creative process; having no formal procedure risked arbitrary choices or no mascot at all; and non-animal options were judged less likely than animals to evoke universality and delight.

No protocol change, retroactive application, current status

This EIP does not directly change the Ethereum protocol; it formalizes a part of the current network upgrade process. Past upgrade mascots that meet the criteria, such as Shapella's owl, are recognized retroactively, and future upgrades from the next hard fork after adoption MUST follow this process. No security considerations are stated. The original text's status is Last Call, with a review deadline of 2026-11-01, not yet finalized. There is no core developer call decision record covering this EIP.

Original EIP · ← EIPs