We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
per #17 (comment) do we want a classification for "contract proposals/standards"?
Another category of Informational EIPs that come to mind, is retrospectives/post-mortems of events like forks, such as https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki, https://blog.ethereum.org/2015/10/22/security-alert-implementation-of-blockhash-instruction-in-c-and-go-clients-can-potentially-cause-consensus-issue-fixed-please-update Would we want these to be Informational EIPs?
The text was updated successfully, but these errors were encountered:
Closing per #183
Sorry, something went wrong.
Merge pull request ethereum#30 from haardikk21/main
935f331
add caip122 spec for eip155 namespace
No branches or pull requests
per #17 (comment) do we want a classification for "contract proposals/standards"?
Another category of Informational EIPs that come to mind, is retrospectives/post-mortems of events like forks, such as https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki, https://blog.ethereum.org/2015/10/22/security-alert-implementation-of-blockhash-instruction-in-c-and-go-clients-can-potentially-cause-consensus-issue-fixed-please-update Would we want these to be Informational EIPs?
The text was updated successfully, but these errors were encountered: