Update EIP-1: Allow links to the Yellow Paper #6834
Conversation
File
|
eth-bot
changed the title
|
I'm strongly against adding the yellow paper preemptively (as discussed on EIPIP). I would like to see something which is not / cannot be expressed in the execution specs, but is expressed in the yellow paper. In my eyes, the yellow paper is a deprecated resource. |
|
On https://github.com/ethereum-cat-herders/EIPIP/issues/226 @SamWilsn and @gcolvin expressed support to allow linking to Yellow Paper . I personally support allowing linking to Yellow Paper.
I believe it's not a policy in EIP-1 or EIP-5757 that a source need to demonstrate another source couldn't express, so I don't think this is a valid argument.
Most of the things in Yellow Paper still holds. I would be interested in seeing when author attempt to link to Yellow Paper to demonstrate some part of the protocol that no longer holds and it's up to our editor's job to point out when a link was incorrectly being linked. |
|
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 was a problem hiding this comment.
This meets the requirements set out by EIP-5757, although since @lightclient is our resident Core dev expert and he suggests it's deprecated as a source, I recommend that all links to it have a warning EIPW annotation attached to them.
FWIW I would love to see the yellow paper updated. I might take that on as a project some time.
|
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. |
|
Closed in favour of #7884 |
Split off from #6306