Something which came out of this for me was how strongly I feel that we are missing safegrounds around the EIP process which are common for mature client codebases. For example, Hyperledger Besu, like all other Linux Foundation projects uses DCO (Developer Certificate of Origin) declarations for all contribution. And those are with real legal names, not pseudonyms.
For EIPs, all we have are required CC0 licensing. No patent protection.
There was a proposal on the patent part, which is good:
But I think we do need to get a lot more risk-focussed, and recognize that the EIP process will be an attack vector for bad actors. Is that the case for ProgPOW? Some people think so, some do not, but the fact is that we don't have consistent armor in our process to defend against these social and political attacks.
Aren't the stakes even higher for the protocol definition than for implementations of that protocol?
INAL, but the protocol doesn’t “belong” to anybody. It’s not a product, it’s a spec.
The nightmare scenario is for patents to get inserted into the protocol.
Lesser scenarios, but which are entirely plausible is for proposals which economically favor particular parties to be inserted by them.
I understand that this stuff is "the whole game" for bodies like the ISO, with companies like IBM being masters at playing it. Pushing "their thing" as a standard, because they have a huge business built on top of that or whatever.
It would be naive to think, with the sums of money at stake around Ethereum, that everybody is going to play fair here. You absolutely will see parties gaming the EIP process.
@bobsummerwill, You are bringing up some very important stuff. We’re working on what were calling the “Ethereum Consensus Project” (https://canonizer.com/topic/210-Ethereum-Consensus-Project/1) at Canonizer.com. It would be great to start a topic to see if some consensus can be built around some of your ideas. For example, we need to get a topic started around the Ether EIP process. Would you mind helping us craft a topic around your ideas so we can find out how many people do and do not agree with this?
Also, as we tweeted here: https://twitter.com/StallionCornell/status/1174439694643298304, we need help tracking consensus for (or against) ProgPoW.