I would also like to see a Discord channel where we can have more fluid discussions around Shanghai planning.
5 Likes
You mean the Discussions-to thread for each EIP?
2 Likes
I’m fine with either adding the topic to the existing threads, like @axic just did, or creating a new one if the EIP champion judges that to be better, like @matt did. The important thing, I think, is for all of the candidates to show up here.
2 Likes
I think this plan makes a lot of sense and I’d support moving ahead with it.
Added shanghai-candidate tag to EIP-4895 discussion: EIP-4895: Beacon chain withdrawals as system-level operations
withdrawals are a must for shanghai
5 Likes
can’t we just use #allcoredevs ?
1 Like
Definitely keen to give this a try and evaluate how it worked. More than just being able to make progress in the Devcon period, it is potentially a good step towards making more ACD discussions async. More async means more time zone, family and work schedule friendly while also creating a better record of the discussion.
4 Likes
after the dust settles
They don’t all show up at https://ethereum-magicians.org/tags/c/eips/core-eips/35/shanghai-candidate. Try https://ethereum-magicians.org/tag/shanghai-candidate.
1 Like
I find #allcoredevs to be a good place to ask general protocol questions and get a relatively quick answer. I am a bit loath to fill that channel with Shanghai planning discussion which I suspect will be a bit voluminous, and potential drown out other protocol questions people have.
Actually, everything except Beacon Chain Withdrawals is an EVM proposal, for which we already have a channel: Discord
Thanks - updated in the first post of this thread!
I’m potentially in favour of this, but I want to make sure it’s something that client teams find valuable and start with what their needs are vs. something that’s first for everyone else and becomes a drag for client teams to keep up with 
Personally I would have thought #allcoredevs was where discussions like what goes into the next hard fork belong (ie stuff that would be discussed on an ACD call) and if we need to we’d split out a different channel for asking protocol questions. The challenge is that as part of doing core dev work there’s a need to understand the protocol and asking in #allcoredevs is good for that, but a general “learn about the Ethereum protocol” is not something core devs will be able to keep up with.
A #protocol-questions type channel is likely to become general community support quite quickly and just be too hard to keep up with. Discord just isn’t the way to scale that kind of learning - it needs something more persistent like blogs, talks etc.
I think we’re maybe misunderstanding each other My rationale for splitting up the channel wasn’t to have somewhere the community can ask protocol questions, but a separate place where we can discuss the “project management” aspect of Shanghai. I’m fine if that’s #allcoredevs, but given that these conversations tend to have high volume, keeping that channel less active might be good.
That said, the risk of another channel dedicated to project management which is open to everyone is that it becomes even higher volume, client teams ignore it, and it’s worse than useless because it’s a productivity drag and paints a picture which doesn’t line up with whaat client teams actually want…!
Re: #shanghai-planning, we agreed to not have it until the ACD calls resume on October 27th, this way people don’t feel they need to monitor a new channel or risk missing changes to the upgrade. We can discuss whether to add the channel on the next ACD.
Not at the moment. It was introduced to support “pull” style withdrawals and we have generally agreed to go the “push” route for handling withdrawals from the CL.
Separately, it would unlock a lot of use cases for staking pools, etc. so I’d love to see some version of this EIP land on-chain eventually. I’d also support inclusion into Shanghai but I’d want to hear more demand in the context of the other priorities before putting more time into moving it along myself.
1 Like