Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update EIP-5218: Renumber to EIP-9 #7396

Closed
wants to merge 2 commits into from
Closed

Conversation

Pandapip1
Copy link
Member

@Pandapip1 Pandapip1 commented Jul 25, 2023

I self-assign myself EIP-9. As per the current EIP-1, I have the power to do this.

I recognize that other editors might feel that this is blatantly self-serving. As such, I will extend to all editors the courtesy of commenting on this number assignment before I merge it. I recommend that any editors believing this to be unfair review #7388.

Have a great day!

Note: This is meant specifically as a demonstration of the absurdity of the current EIP rules. If this renumbering somehow does get merged, I will re-assign it EIP-5218 and contemplate the nature of reality.

@eth-bot
Copy link
Collaborator

eth-bot commented Jul 25, 2023

File EIPS/eip-5218.md

Requires 1 more reviewers from @grimmelm, @iseriohn, @relyt29

@Pandapip1 Pandapip1 added the e-review Waiting on editor to review label Jul 25, 2023
@github-actions
Copy link

The commit 94b7d21 (as a parent of 56db02f) contains errors.
Please inspect the Run Summary for details.

@github-actions github-actions bot added the w-ci Waiting on CI to pass label Jul 25, 2023
@github-actions github-actions bot added c-update Modifies an existing proposal s-draft This EIP is a Draft t-erc labels Jul 25, 2023
@eth-bot eth-bot changed the title Update EIP-5289: Renumber to EIP-9 Update EIP-5218: Renumber to EIP-9 Jul 25, 2023
@eth-bot eth-bot added a-review Waiting on author to review and removed e-review Waiting on editor to review labels Jul 25, 2023
@github-actions github-actions bot removed the w-ci Waiting on CI to pass label Jul 25, 2023
@lightclient
Copy link
Member

With power comes responsibility.

@Pandapip1
Copy link
Member Author

With power comes responsibility.

Agreed. Therefore, we should limit editors' number assigning powers to something more reasonable.

@lightclient
Copy link
Member

lightclient commented Jul 25, 2023

Or we should have editors who don't need their assignment power curtailed, because they are responsible with the power and operate always in the interest of the community.

@Pandapip1
Copy link
Member Author

Pandapip1 commented Jul 25, 2023

Or we should have editors who don't need their assignment power curtailed, because they are responsible with the power and operate always in the interest of the community.

A large portion of the community disagrees with your assignment of EIP-5000, myself included. I nonetheless am not advocating for your removal. If a system can be abused, then that's a problem with the system, not the people in it.

That is the entire premise for the existence of the Ethereum Consensus Layer: it's a system that has enough rules that the extent to which it can be abused is minimal. Otherwise, there's no reason Ethereum couldn't be operated using PoA.

@lightclient
Copy link
Member

A large portion of the community disagrees with your assignment of EIP-5000

Where are they? As usual, it is just EIP editors and few people who clearly opened spam before their PR was opened and they didn't get the number they wanted. The majority of the community doesn't care about EIP numbers.

That is the entire premise for the existence of the Ethereum Consensus Layer

EIP editing isn't a consensus mechanism, wasn't designed to be one, and shouldn't aim to become one. We are professionals trying to document change proposals to Ethereum as best we can.

@Pandapip1
Copy link
Member Author

Where are they?

The following is a list of people that disagreed with your decision to assign EIP-5000:

The following is a list of people that want a clear policy for EIP numbering:

[a] few people who clearly opened spam before their PR was opened and they didn't get the number they wanted

I wasn't able to find any non-editors supporting my position, not even spammers.

The majority of the community doesn't care about EIP numbers.

You clearly do, since you (rightfully) disagree with this PR. Additionally, I do not believe there to be evidence to support or dismiss this statement. CC @poojaranjan?

EIP editing ... wasn't designed to be [a consensus mechanism]

I wasn't there when the EIPs repository was formed. If you know this to be true, I will defer to you.

EIP editing isn't a consensus mechanism

EIP editing has nonetheless acquired a consensus mechanism.

We are professionals trying to document change proposals to Ethereum as best we can.

I approve of this statement.


You seem to support the position of "if I have the authority to do it, then it should be allowed": #5270 (comment). If you have since changed your mind, or I am somehow not picking up on some nuance, please correct me.

I'm going to stop debating now, and since I believe my point has been sufficiently made, I'll close this PR. Please continue discussion at the other PR: #7388

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a-review Waiting on author to review c-update Modifies an existing proposal s-draft This EIP is a Draft t-erc
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants