Skip to content

Commit 46d1ddc

Browse files
committed
simplified & made informational
1 parent d4ad3cd commit 46d1ddc

File tree

1 file changed

+7
-19
lines changed

1 file changed

+7
-19
lines changed

EIPS/eip-8066.md

Lines changed: 7 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -5,14 +5,14 @@ description: Process for assigning a mascot to each Ethereum network upgrade
55
author: Jordan Holberg (@eviljordan), Andrew B Coathup (@abcoathup)
66
discussions-to: https://ethereum-magicians.org/t/eip-8066-upgrade-mascots/26009
77
status: Draft
8-
type: Meta
8+
type: Informational
99
created: 2024-10-29
1010
requires:
1111
---
1212

1313
## Abstract
1414

15-
This Meta EIP establishes a standardized process for assigning a mascot to each Ethereum network upgrade. Mascots serve to humanize and celebrate upgrades, fostering community engagement while adhering to principles of cuteness, relevance, and inclusivity. The mascot is selected by a designated facilitator (the "Mascot Wrestler") through community-driven processes, with safeguards for appropriateness.
15+
This EIP establishes a mascot for each Ethereum network upgrade. Mascots serve to humanize and celebrate upgrades, fostering community engagement while adhering to principles of cuteness, relevance, and inclusivity. The mascot is selected through community-driven processes, with safeguards for appropriateness, by a designated facilitator (the "Mascot Wrestler").
1616

1717
## Motivation
1818

@@ -22,8 +22,6 @@ Ethereum network upgrades often introduce complex technical changes that can fee
2222
- Creates opportunities for creative expression in upgrade event branding, merchandise, and digital collectibles (e.g., POAPs).
2323
- Builds a consistent, whimsical tradition that differentiates Ethereum's upgrade narrative from other ecosystems.
2424

25-
Without a formalized process, mascot selection risks inconsistency or neglect, diminishing their potential impact.
26-
2725
## Specification
2826

2927
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174.
@@ -35,21 +33,17 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S
3533
- **Tone**: The mascot **MUST NOT** be offensive (no depictions of violence, discrimination, or controversy) and **SHOULD** be inherently cute (e.g., avoiding aggressive or fearsome traits unless softened for adorability).
3634

3735
### 2. Roles and Responsibilities
38-
- **Mascot Wrestler**: A self-selected community facilitator responsible for proposing, selecting, and adopting the mascot for a network upgrade. The Mascot Wrestler self-nominates. The role **MAY** rotate voluntarily per upgrade cycle to encourage diverse participation.
36+
- **Mascot Wrestler**: A self-selected community facilitator responsible for proposing, selecting, and adopting the mascot for a network upgrade. The role **MAY** rotate voluntarily per upgrade cycle to encourage diverse participation.
3937
- Duties include:
4038
- Soliciting and curating mascot candidates.
4139
- Facilitating selection processes.
4240
- Announcing the final mascot (e.g., Ethereum Magicians, All Core Devs).
4341
- **Veto Powers**:
44-
- The Mascot Wrestler *MAY** veto any candidate mascot deemed inappropriate based on the requirements above.
42+
- The Mascot Wrestler **MAY** veto any candidate mascot not meeting the mascot requirements above.
4543
- A rough consensus of client teams **MAY** veto the selected mascot, triggering fallback to the next-highest-ranked candidate mascot.
4644

4745
### 3. Selection Process
48-
The Mascot Wrestler shall conduct selection using one or more community-appropriate mechanisms, aiming for inclusivity and transparency:
49-
- **Public Signaling Polls**: On platforms like Ethereum Magicians Forum, Forkcast, or social media.
50-
- **OnChain Voting**
51-
- **Prediction Markets**: where market resolution determines the winner.
52-
- **Other Mechanisms**: Any fair, auditable process that allows broad participation.
46+
The Mascot Wrestler **SHALL** conduct selection using one or more community-appropriate mechanisms.
5347

5448
The process **MUST**:
5549
- Run for a minimum of 7 days.
@@ -60,13 +54,8 @@ The process **MUST**:
6054
If no consensus is reached, the Mascot Wrestler selects the top candidate by default, subject to veto.
6155

6256
### 4. Usage Guidelines
63-
Adopted upgrade mascots **MAY** be used to celebrate the upgrade in:
64-
- **Logs and Announcements**: ASCII art in client logs, devnet announcements, and release notes.
65-
- **Events and Collectibles**: POAPs, conference swag, or virtual badges featuring the mascot.
66-
- **Merchandise**: community-created items (e.g., stickers, t-shirts), with attribution to the Mascot Wrestler and community contributors.
67-
- **Branding**: Integration into upgrade roadmaps, blog posts, and social media campaigns.
6857

69-
All uses must respect the network upgrade mascot's cute, non-offensive nature and credit original concept creators where applicable.
58+
All uses **MUST** respect the network upgrade mascot's cute, non-offensive nature and credit original concept creators where applicable.
7059

7160
## Rationale
7261

@@ -79,8 +68,7 @@ Alternatives considered:
7968

8069
## Backwards Compatibility
8170

82-
This EIP does not directly change the Ethereum protocol. It formalizes part of the current network upgrade process. Past upgrades (e.g., Shapella's owl :owl:, Dencun's blowfish :blowfish:) are retroactively honored if they fit the criteria; future upgrades **MUST** comply starting with the next hard fork post-adoption.
83-
71+
This EIP does not directly change the Ethereum protocol. It formalizes part of the current network upgrade process. Past upgrades (e.g., Shapella's owl :owl:) are retroactively honored if they fit the criteria; future upgrades **MUST** comply starting with the next hard fork post-adoption.
8472

8573
## Security Considerations
8674

0 commit comments

Comments
 (0)