-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
move eip-712 to Last Call #4383
Conversation
Hi! I'm a bot, and I wanted to automerge your PR, but couldn't because of the following issue(s): (fail) eip-712.md
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only review Core EIPs, so just a few comments here to help facilitate moving this along:
Simple Summary
section has been removed.- A new
description
header field has been added that should contain a human readable one-line description of the EIP. - Remove external links. Inline things as appropriate or just remove the reference entirely.
- Remove the
Implementation
section. This isn't a valid EIP section (also, the content in it isn't appropriate for an EIP). - Add missing Security Considerations section above Copyright section.
Rationale for domainSeparator
needs an extra#
leading it.
Thanks @MicahZoltu ! I forgot to check back for comments until now, I'll get to work on these when I can. |
I'm working with Recmo to try and accommodate Micah's suggestions. Most are simple fixes, others are more complicated, particularly the external links one, which would require a significant amount of editing, and really even changing the way the EIP looks today. (Unless there's something I'm misunderstanding, which is totally possible.) |
Head branch was pushed to by a user without write access
(The most recent push should implement everything other than the external links, let me know if I missed something. Still working on finding a good solution on the links.) |
Could we also point the link to the JSON-RPC spec to https://github.com/ethereum/execution-apis? Looks good to me otherwise. |
Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - @recmo could you approve to move this forward? Thanks.
@recmo bump |
Not really stale, but waiting on authors (@recmo, @LogvinovLeon, @dekz). |
Also, if you're interested @wschwab, you should add yourself as an author. |
Given the length of time that this EIP has taken - and the lack of response from @recmo - with it languishing for years now, the fact that we can't move the status forward without an author approving, and that this is becoming something of a bureaucratic blocker for other EIPs, might I propose that this is effectively 'forked' into a new EIP with authors more amenable to ticking the boxes required so that it can be finalised at last? @wschwab can't add himself as an author to this EIP without a PR (whether or not he feels like he deserves this due to the nature of his contribution is somewhat by-the-by): that in and of itself requires the approval of an author. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the simplest way for me to bump the date up, sorry for the clutter
okay, I thought it was the simplest way to bump the last call date, but it seems to have gone completely off the rails, I'm trying to fix it up |
okay, now I'm actually really confused - it looks like someone got 712 to Last Call, trying to figure out when and how it happened |
No description provided.