It is clear from the ProgPow debacle that we need accountability more than ever when deciding which EIPs are accepted and are actually implemented. The biggest barrier seems to be trust, and from my understanding and brief research, there is no list of Ethereum Core Devs or even a clear process defined to become one. (See @ameensol am i core dev meme) The wider community (dapp developers, shit coin shillers, miners, os contributors, etc) have no idea who these people are, what are their motives, who do they work for, what EIPs have they supported in the past or have campaigned against.
This has led to the rise of twitter governance as some sort of arbiter of sentiment, when I believe we should be embracing some democratic process to determine who should be considered a core dev, and to start keeping track of support history of particular EIPs. While I understand this is controversial position to take, especially coming from someone outside this small community, in the long run it will bring credibility to the process, and an ability for the existing expert technical members to steer governance decisions in a way that can beneficial for the network as a whole and all of its participants.
I suggest that we start collecting the information of the existing core devs and having them use signed keys that they will use to vote in a Ranked Pair mechanism where they can signal which EIPs they support by moving all non-draft EIPs to a pointer on chain. We can either have @souptacular be the owner of this contract given he has write-access of PM start running elections and creating a whitelist of addresses that the community can vet using the one of many DID standards that have been floating around, where they can sign a standardized document that has the answers to the questions above as well as seniority / what projects they are actively contributed to / who is funding them. @oed @jbaylina @GriffGreen
Or instead of trusting one person to be a good guy ™, and set up these contracts at regular intervals, we start airdropping NFTs to those whitelisted addresses and have a factory contract that spins up an election over some arbitrary cycle and use those tokens as tickets to entry.
It would be awesome if the conversation of what goes into this document happened in this thread so privacy grievances can be aired. Furthermore, if enough core devs / EF / EthMagicians / Consensys / whoever runs this shitshow comes to a consensus that this mechanism would be useful, we can run parallel elections where representatives of projects in let’s say this registry: https://everest.link/ (@evabeylin idk Yaniv’s account) can have a vote and we weigh the results against each other. Let’s discuss what a fair ratio of that should be.
Here’s a repo with a contract if anyone wants to help build this: https://github.com/corydickson/ranked-pairs-voting
A dapp would be nice that aggregated this info
btw all of the flaws in this mechanism are alleviated by the fact the state of the election is known to all potential voters at any given block height. I also think that this is real consensus as @gcolvin described here: there aren’t black and white decisions but instead a gradient of support.
tldr: Core Devs should vote on which EIPs go into the accepted state and this should be transparent and put on-chain