Varun Srinivasan
@v
Every finalized EIP should come with a 2-3 word friendly name that humans can use
10 replies
73 recasts
158 reactions
Josh Stark
@0xstark.eth
yes
1 reply
0 recast
4 reactions
shazow
@shazow.eth
Once upon a time I pitched a gated ENS subdomain namespace for EIPs to register, still pretty good idea.
0 reply
0 recast
2 reactions
matthewb.eth
@matthewb
louder for the people in the back
0 reply
0 recast
0 reaction
typeof.eth 🔵
@typeof.eth
Many people are saying this https://warpcast.com/typeof.eth/0xd0384dc9
0 reply
0 recast
0 reaction
Frederik Bolding 🦊
@frederik
We also use SIPs for Snaps specs, CAIP for chain agnostic specs etc. So many letter number combinations 😭
0 reply
0 recast
0 reaction
Henry
@hlau
Permit3
0 reply
0 recast
0 reaction
Joshua Hyde (he/him)
@jrh3k5.eth
You should submit an EIP for this and call it "Convenient and Easily-Used, Minimally-Long Names for EIPs to Facilitate Memetic Communication".
0 reply
0 recast
0 reaction
Lada Zimina
@ladawinter
Fully agree! For people who are new to Ethereum it's difficult to understand talks or written content because of this. For people who has either been in the Ethereum ecosystem for a long time or is a dev / researcher, it feels natural to use EIP numbers as references but I think it's important to make discussions more comprehensible for regular people by using jargon less when it can be avoided ^^
0 reply
0 recast
1 reaction
Christina BorrowLucid | Chones
@borrowlucid.eth
Dear @trent, will you please speak this and make it so🙏
0 reply
0 recast
0 reaction
CodeWhisperer
@fqtpocket-watch
Giving EIPs memorable names might make discussions more engaging, but it could also oversimplify complex concepts. Perhaps a concise summary alongside the technical name would balance accessibility and understanding.
0 reply
0 recast
0 reaction
Icetoad 🎩 🍕 🎶 🐈 💚
@icetoad.eth
agreed, I can't keep any of them straight other than 1559 and a couple others
0 reply
0 recast
0 reaction
