Software Release CAIP #238
Conversation
A proposal on how we can lay a solid foundation for requesting chain software information alongside a standard data structure for response payloads. The hope is that this can lay a foundation on which systems can be built that address ongoing issues for node runners and validator operators know about and automatically executing on software release events.
|
Hey sorry I'm a little lost on context here. Is this Ethereum-specific? Would it make sense to try to get support for this in, say, the AllCoreDevs discord of the Ethereum Foundation if so, or in the equivalent repo/community forum where protocol upgrades are designed and aligned in some other namespace first, and then bring a generalized v2 back afterwards with some implementer feedback and lessons learned? |
|
It is not ethereum specific, the problem exists in every network as far as I've experienced. |
|
OK! Is there anything similar implemented in the wild that this is an improvement on? Or do you know of other VMs/ecosystems/"namespaces" that have a use-case for this and are interested in specifying it before or after implementing? If you look in the open PRs, there are a few other, similar ideas (many of them authored by me!) which are similarly waiting for an implementer-champion, because we prefer not to specify pure greenfield at CASA, so much as things that at least 1, preferably 2 independent implementations are at least softly-commited to taking to production... |
|
Sounds good! I'll take a look through and see what I can find. |
|
absolutely! feel free to book something at cal.com/ and bring as much or as little of your team as you think would be constructive 😄 |
whoops my cal.com was misconfigured and swallowing requests without throwing, if you already made an appointment it was lost. could I ask you to try again if so? |
|
@null-ref-ex any progress here? i'll be in US time zones starting in 2 weeks so glad to take any joint calls with partners that are curious about the idea. apologies that I forgot about this and didn't ask around at Devconnect like I hoped to! |
|
@null-ref-ex thought of you the other day: (See also the eth-mag thread) |
|
A proposal on how we can lay a solid foundation for requesting chain software information alongside a standard data structure for response payloads. The hope is that this can lay a foundation on which systems can be built that address ongoing issues for node runners and validator operators know about and automatically executing on software release events.