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

EIP Author's Manual #1014

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

gurukamath
Copy link
Collaborator

First draft of the EIP authors manual. Looking for suggestions for improvement, things that can be added, removed, re-done etc.

@poojaranjan
Copy link
Collaborator

Helpful document. I wonder if we should have it as an EIP? cc: @SamWilsn @lightclient

EIP_AUTHORS_MANUAL.md Outdated Show resolved Hide resolved

# Forks under development

At the time of writing, the Prague Fork is still under development and the previous fork is Cancun, which is live on Mainnet.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will constantly forget to update this. Probably better to omit references to specific forks.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this needs to be updated at all. I was intending for this to just be a concrete example of the folder structure for the fork under development. Perhaps the fact that this is just an example is unclear from the text. I have updated the text to make that fact more explicit.

@SamWilsn
Copy link
Collaborator

@poojaranjan That's a good idea. If EELS reference implementations become mandatory, we'll have to move this to EIP-1.

Let's leave it here for now, with the intent to move it later?

Copy link
Collaborator

@petertdavies petertdavies left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great! It sets out the proposed process in a really clear and concise manner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants