EIPs
EIPs copied to clipboard
ethereum
Update EIP-1: Explicitly state that backward compatible errata are allowed for final EIPs
File EIPS/eip-1.md
Requires 1 more reviewers from @SamWilsn, @axic, @lightclient
At the very least it's hard to determine whether something is backward compatible.
I've love to voice my opposition to this change without boarder EIP Editor group consensus.
Could I suggest you instead start an informational EIP that gives examples of what's considered backward compatible or not, before making it a EIP-1 rule?
Backward compatibility has a very simple definition: if a particular behavior has a satisfiable unambiguous definition, then it can't be changed.
Most often I'd envision a change from author like "hey I want to add this method (but optional/extension) to the ERC interface"
Do we count this type of change as "backward compatible"?
Do we count this type of change as "backward compatible"?
That's a really good point. I would say that it wouldn't be backward compatible in the majority of the cases since it's pretty standard to use EIP-165. Not sure about other cases - I'll have to revise the definition.
How about:
If a particular behavior has a satisfiable unambiguous definition, then it can't be changed. If a particular behavior has no definition, then one can't be added. If a particular behavior has a definition that is either unsatisfiable or ambiguous, then it may be changed.
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.
There has been no activity on this pull request for 2 weeks. It will be closed after 3 months of inactivity. If you would like to move this PR forward, please respond to any outstanding feedback or add a comment indicating that you have addressed all required feedback and are ready for a review.
This pull request was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback or request a review in a comment.