mirror of https://github.com/status-im/EIPs.git
Nick Johnson
GitHub
commit
06df3ce690
|
|
@ -0,0 +1,16 @@
|
|||
#!/bin/bash
|
||||
set -e # halt script on error
|
||||
|
||||
HTMLPROOFER_OPTIONS="./_site --internal-domains=eips.ethereum.org --check-html --check-opengraph --report-missing-names --log-level=:debug --assume-extension --empty-alt-ignore --url-ignore=/EIPS/eip-1,EIPS/eip-1,/EIPS/eip-107,/EIPS/eip-858"
|
||||
|
||||
bundle exec jekyll doctor
|
||||
bundle exec jekyll build
|
||||
|
||||
if [[ $TASK = 'htmlproofer' ]]; then
|
||||
bundle exec htmlproofer $HTMLPROOFER_OPTIONS --disable-external
|
||||
elif [[ $TASK = 'htmlproofer-external' ]]; then
|
||||
bundle exec htmlproofer $HTMLPROOFER_OPTIONS --external_only
|
||||
fi
|
||||
|
||||
# Validate GH Pages DNS setup
|
||||
bundle exec github-pages health-check
|
||||
|
|
@ -0,0 +1,25 @@
|
|||
sudo: false # route your build to the container-based infrastructure for a faster build
|
||||
|
||||
language: ruby
|
||||
|
||||
# Cache Ruby bundles
|
||||
cache: bundler
|
||||
|
||||
# Assume bundler is being used, therefore
|
||||
# the `install` step will run `bundle install` by default.
|
||||
script: "bash -ex .travis-ci.sh"
|
||||
|
||||
env:
|
||||
global:
|
||||
- NOKOGIRI_USE_SYSTEM_LIBRARIES=true # speeds up installation of html-proofer
|
||||
|
||||
matrix:
|
||||
fast_finish: true
|
||||
include:
|
||||
- rvm: 2.2.5
|
||||
env: TASK='htmlproofer'
|
||||
- rvm: 2.2.5
|
||||
env: TASK='htmlproofer-external'
|
||||
allow_failures:
|
||||
- rvm: 2.2.5
|
||||
env: TASK='htmlproofer-external'
|
||||
|
|
@ -62,7 +62,7 @@ EIPs can also be superseded by a different EIP, rendering the original obsolete.
|
|||
|
||||
The possible paths of the status of EIPs are as follows:
|
||||
|
||||
|
||||
|
||||
|
||||
Some Informational and Process EIPs may also have a status of “Active” if they are never meant to be completed. E.g. EIP 1 (this EIP).
|
||||
|
||||
|
|
@ -220,10 +220,6 @@ Once the EIP is ready for the repository, the EIP editor will:
|
|||
|
||||
<!-- -->
|
||||
|
||||
- List the EIP in [README.md]
|
||||
|
||||
<!-- -->
|
||||
|
||||
- Send a message back to the EIP author with next step.
|
||||
|
||||
Many EIPs are written and maintained by developers with write access to the Ethereum codebase. The EIP editors monitor EIP changes, and correct any structure, grammar, spelling, or markup mistakes we see.
|
||||
|
|
@ -239,6 +235,8 @@ December 7, 2016: EIP 1 has been improved and will be placed as a PR.
|
|||
|
||||
February 1, 2016: EIP 1 has added editors, made draft improvements to process, and has merged with Master stream.
|
||||
|
||||
March 21, 2018: Minor edits to accommodate new automatically-generated EIP directory on eips.ethereum.org.
|
||||
|
||||
[EIP5]: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-5.md
|
||||
[EIP101]: https://github.com/ethereum/EIPs/issues/28
|
||||
[EIP90]: https://github.com/ethereum/EIPs/issues/90
|
||||
|
|
@ -266,7 +264,6 @@ February 1, 2016: EIP 1 has added editors, made draft improvements to process, a
|
|||
[formal specification]: https://github.com/ethereum/yellowpaper
|
||||
[the Issues section of this repository]: https://github.com/ethereum/EIPs/issues
|
||||
[markdown]: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
|
||||
[README.md]: README.md "wikilink"
|
||||
[Bitcoin's BIP-0001]: https://github.com/bitcoin/bips
|
||||
[Python's PEP-0001]: https://www.python.org/dev/peps/
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
eip: 101
|
||||
title: Serenity Currency and Crypto Abstraction
|
||||
author: Vitalik Buterin <v@buterin.com>
|
||||
status: Active
|
||||
status: Draft
|
||||
type: Standards Track
|
||||
category: Core
|
||||
created: 2015-11-15
|
||||
|
|
|
|||
|
|
@ -29,19 +29,19 @@ Account unlocked :
|
|||
-----------------
|
||||
When the account is already unlocked, the user is presented with the following popup for every transaction that the dapp attempts to make:
|
||||
|
||||
|
||||
|
||||
|
||||
Account locked and no "personal" api exposed via rpc:
|
||||
-----------------
|
||||
When the account is locked, and the node does not provide access to account unlocking via its rpc interface, the following popup will be presented. This is not ideal since this requires the user to know how to unlock an account:
|
||||
|
||||
|
||||
|
||||
|
||||
Account locked but node exposing the "personal" api via rpc :
|
||||
-----------------
|
||||
A better option is to ask the user for their password, but this is only possible if the node allows access to the "personal" api via rpc. In such case, the following dialog will be presented to the user so he/she can accept the transaction by providing the password required to unlock the account:
|
||||
|
||||
![](authorization-password.png")
|
||||
|
||||
|
||||
|
||||
Specification
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
eip: 140
|
||||
title: REVERT instruction
|
||||
author: Alex Beregszaszi, Nikolai Mushegian (nikolai@nexusdev.us)
|
||||
author: Alex Beregszaszi, Nikolai Mushegian <nikolai@nexusdev.us>
|
||||
type: Standards Track
|
||||
category: Core
|
||||
status: Final
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ title: State clearing
|
|||
author: Vitalik Buterin
|
||||
type: Standards Track
|
||||
category: Core
|
||||
status: Superseded
|
||||
status: Replaced
|
||||
created: 2016-10-16
|
||||
superseded-by: 161
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
eip: 190
|
||||
title: Ethereum Smart Contract Packaging Standard
|
||||
Authors: Piper Merriam, Tim Coulter, Denis Erfurt (mhhf), RJ Catalano (VoR0220), Iuri Matias (iurimatias)
|
||||
author: Piper Merriam, Tim Coulter, Denis Erfurt (mhhf), RJ Catalano (VoR0220), Iuri Matias (iurimatias)
|
||||
status: Final
|
||||
type: Standards Track
|
||||
category: ERC
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ type: Standards Track
|
|||
category: Core
|
||||
status: Final
|
||||
created: 2017-02-13
|
||||
replaces: 5,8
|
||||
replaces: 5
|
||||
---
|
||||
|
||||
## Simple Summary
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ layer: Process
|
|||
title: EIP Classification
|
||||
author: Joseph Chow
|
||||
status: Draft
|
||||
type: Process
|
||||
type: Meta
|
||||
created: 2015-11-17
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,12 +1,11 @@
|
|||
---
|
||||
eip: 649
|
||||
title: Metropolis Difficulty Bomb Delay and Block Reward Reduction
|
||||
Authors: Afri Schoedon, Vitalik Buterin
|
||||
author: Afri Schoedon, Vitalik Buterin
|
||||
type: Standards Track
|
||||
category: Core
|
||||
status: Final
|
||||
created: 2017-06-21
|
||||
replaces: 186
|
||||
---
|
||||
|
||||
## Simple Summary
|
||||
|
|
|
|||
|
|
@ -7,7 +7,6 @@ category: Core
|
|||
status: Final
|
||||
created: 2017-06-30
|
||||
requires: 140
|
||||
replaces: 98
|
||||
---
|
||||
|
||||
## Abstract
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
eip: 695
|
||||
title: Create `eth_chainId` method for JSON-RPC
|
||||
author: Isaac Ardis <isaac.ardis@gmail.com> Wei Tang <hi@that.world>, @tcz001 <https://github.com/tcz001>
|
||||
author: Isaac Ardis <isaac.ardis@gmail.com> Wei Tang <hi@that.world>, @tcz001
|
||||
type: Standards Track
|
||||
category: Interface
|
||||
status: Draft
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ type: Standards Track
|
|||
category: ERC
|
||||
status: Draft
|
||||
created: 2018-01-24
|
||||
requires: ERC-165
|
||||
requires: 165
|
||||
---
|
||||
|
||||
## Simple Summary
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ eip: 778
|
|||
title: Ethereum Node Records (ENR)
|
||||
author: Felix Lange <fjl@ethereum.org>
|
||||
type: Standard Track
|
||||
category Networking
|
||||
category: Networking
|
||||
status: Draft
|
||||
created: 2017-11-23
|
||||
---
|
||||
|
|
@ -101,4 +101,3 @@ additional metadata.
|
|||
# Copyright
|
||||
|
||||
Copyright and related rights waived via CC0.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ title: devp2p Forward Compatibility Requirements for Homestead
|
|||
author: Felix Lange <felix@ethdev.com>
|
||||
status: Final
|
||||
type: Standards Track
|
||||
layer: Networking
|
||||
category: Networking
|
||||
created: 2015-12-18
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ Reduce the block reward to 1 ETH.
|
|||
The current public Ethereum network has a hashrate that corresponds to a tremendous level of energy consumption. As this energy consumption has a correlated environmental cost the network participants have an ethical obligation to ensure this cost is not higher than necessary. At this time, the most direct way to reduce this cost is to lower the block reward in order to limit the appeal of ETH mining. Unchecked growth in hashrate is also counterproductive from a security standpoint.
|
||||
|
||||
## Motivation
|
||||
The current public Ethereum network has a hashrate of 232 TH/s). This hashrate corresponds to a **lower bound** for power usage of roughly [821 MW](calculations.md) and yearly energy consumption of 7.2 TWh (roughly 0.033% of [total](https://en.wikipedia.org/wiki/List_of_countries_by_electricity_consumption) global electricity consumption). A future switch to full Proof of Stake will solve this issue entirely. Yet that switch remains enough in the future that action should be taken in the interim to limit excess harmful side affects of the present network.
|
||||
The current public Ethereum network has a hashrate of 232 TH/s). This hashrate corresponds to a **lower bound** for power usage of roughly [821 MW](eip-858/calculations.md) and yearly energy consumption of 7.2 TWh (roughly 0.033% of [total](https://en.wikipedia.org/wiki/List_of_countries_by_electricity_consumption) global electricity consumption). A future switch to full Proof of Stake will solve this issue entirely. Yet that switch remains enough in the future that action should be taken in the interim to limit excess harmful side affects of the present network.
|
||||
|
||||
## Specification
|
||||
Block reward to be changed to 1 ETH / block.
|
||||
|
|
|
|||
2
Gemfile
2
Gemfile
|
|
@ -28,3 +28,5 @@ gem "tzinfo-data", platforms: [:mingw, :mswin, :x64_mingw, :jruby]
|
|||
|
||||
# Performance-booster for watching directories on Windows
|
||||
gem "wdm", "~> 0.1.0" if Gem.win_platform?
|
||||
|
||||
gem "html-proofer", '>=3.3.1'
|
||||
|
|
|
|||
13
Gemfile.lock
13
Gemfile.lock
|
|
@ -13,6 +13,7 @@ GEM
|
|||
execjs
|
||||
coffee-script-source (1.11.1)
|
||||
colorator (1.1.0)
|
||||
colorize (0.8.1)
|
||||
commonmarker (0.17.9)
|
||||
ruby-enum (~> 0.5)
|
||||
concurrent-ruby (1.0.5)
|
||||
|
|
@ -78,6 +79,15 @@ GEM
|
|||
html-pipeline (2.7.1)
|
||||
activesupport (>= 2)
|
||||
nokogiri (>= 1.4)
|
||||
html-proofer (3.8.0)
|
||||
activesupport (>= 4.2, < 6.0)
|
||||
addressable (~> 2.3)
|
||||
colorize (~> 0.8)
|
||||
mercenary (~> 0.3.2)
|
||||
nokogiri (~> 1.8.1)
|
||||
parallel (~> 1.3)
|
||||
typhoeus (~> 1.3)
|
||||
yell (~> 2.0)
|
||||
i18n (0.9.5)
|
||||
concurrent-ruby (~> 1.0)
|
||||
jekyll (3.6.2)
|
||||
|
|
@ -204,6 +214,7 @@ GEM
|
|||
mini_portile2 (~> 2.3.0)
|
||||
octokit (4.8.0)
|
||||
sawyer (~> 0.8.0, >= 0.5.3)
|
||||
parallel (1.12.1)
|
||||
pathutil (0.16.1)
|
||||
forwardable-extended (~> 2.6)
|
||||
public_suffix (2.0.5)
|
||||
|
|
@ -232,12 +243,14 @@ GEM
|
|||
tzinfo (1.2.5)
|
||||
thread_safe (~> 0.1)
|
||||
unicode-display_width (1.3.0)
|
||||
yell (2.0.7)
|
||||
|
||||
PLATFORMS
|
||||
ruby
|
||||
|
||||
DEPENDENCIES
|
||||
github-pages
|
||||
html-proofer (>= 3.3.1)
|
||||
jekyll (~> 3.6.2)
|
||||
jekyll-feed (~> 0.6)
|
||||
minima (~> 2.0)
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ description: >-
|
|||
Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum
|
||||
platform, including core protocol specifications, client APIs, and contract
|
||||
standards.
|
||||
url: "" # the base hostname & protocol for your site, e.g. http://example.com
|
||||
url: "http://eips.ethereum.org"
|
||||
twitter_username: ethereum
|
||||
github_username: ethereum
|
||||
header_pages:
|
||||
|
|
@ -36,7 +36,7 @@ theme: minima
|
|||
plugins:
|
||||
- jekyll-feed
|
||||
|
||||
permalink: slug
|
||||
permalink: /:slug
|
||||
|
||||
defaults:
|
||||
-
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
{% assign eips=include.eips|split:"," %}
|
||||
{% for eipnum in eips %}
|
||||
<a href="{{eipnum|strip|prepend:"eip-" }}">{{eipnum}}</a>{% if forloop.last == false %}, {% endif %}
|
||||
<a href="{{eipnum|strip|prepend:"eip-" }}">{{eipnum|strip}}</a>{% if forloop.last == false %}, {% endif %}
|
||||
{% endfor %}
|
||||
|
|
|
|||
|
|
@ -3,8 +3,6 @@ layout: default
|
|||
title: Home
|
||||
---
|
||||
|
||||
<a href="{{site.github.repository_url}}"><img style="position: absolute; top: 0; right: 0; border: 0;" src="https://s3.amazonaws.com/github/ribbons/forkme_right_darkblue_121621.png" alt="Fork me on GitHub"></a>
|
||||
|
||||
<h1 class="page-heading">EIPs <a href="https://gitter.im/ethereum/EIPs?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge"><img src="https://badges.gitter.im/Join%20Chat.svg" alt="Gitter"></a></h1>
|
||||
<p>Ethereum Improvement Proposals (EIPs) describe standards for the Ethereum platform, including core protocol specifications, client APIs, and contract standards.</p>
|
||||
|
||||
|
|
@ -27,16 +25,16 @@ title: Home
|
|||
<p>Describes any change that affects most or all Ethereum implementations, such as a change to the the network protocol, a change in block or transaction validity rules, proposed application standards/conventions, or any change or addition that affects the interoperability of applications using Ethereum. Furthermore Standard EIPs can be broken down into the following categories.</p>
|
||||
|
||||
<h4><a href="{{"core"|relative_url}}">Core</a> ({{site.pages|where:"type","Standards Track"|where:"category","Core"|size}})</h4>
|
||||
<p>Improvements requiring a consensus fork (e.g. <a href="EIPS/eip-5">EIP5</a>, <a href="EIPS/eip-101">EIP101</a>), as well as changes that are not necessarily consensus critical but may be relevant to “core dev” discussions (for example, <a href="EIPS/eip-90">EIP90</a>, and the miner/node strategy changes 2, 3, and 4 of <a href="EIPS/eip-86">EIP86</a>).</p>
|
||||
<p>Improvements requiring a consensus fork (e.g. <a href="EIPS/eip-5">EIP5</a>, <a href="EIPS/eip-101">EIP101</a>), as well as changes that are not necessarily consensus critical but may be relevant to “core dev” discussions (for example, the miner/node strategy changes 2, 3, and 4 of <a href="EIPS/eip-86">EIP86</a>).</p>
|
||||
|
||||
<h4><a href="{{"networking"|relative_url}}">Networking</a> ({{site.pages|where:"type","Standards Track"|where:"category","Networking"|size}})</h4>
|
||||
<p>Includes improvements around devp2p (<a href="EIPS/eip-8">EIP8</a>) and Light Ethereum Subprotocol, as well as proposed improvements to network protocol specifications of whisper and swarm.</p>
|
||||
|
||||
<h4><a href="{{"interface"|relative_url}}">Interface</a> ({{site.pages|where:"type","Standards Track"|where:"category","Interface"|size}})</h4>
|
||||
<p>Includes improvements around client API/RPC specifications and standards, and also certain language-level standards like method names (<a href="EIPS/eip-59">EIP59</a>, <a href="EIPS/eip-6">EIP6</a>) and contract ABIs. The label “interface” aligns with the interfaces repo and discussion should primarily occur in that repository before an EIP is submitted to the EIPs repository.</p>
|
||||
<p>Includes improvements around client API/RPC specifications and standards, and also certain language-level standards like method names (<a href="EIPS/eip-6">EIP6</a>) and contract ABIs. The label “interface” aligns with the interfaces repo and discussion should primarily occur in that repository before an EIP is submitted to the EIPs repository.</p>
|
||||
|
||||
<h4><a href="{{"erc"|relative_url}}">ERC</a> ({{site.pages|where:"type","Standards Track"|where:"category","ERC"|size}})</h4>
|
||||
<p>Application-level standards and conventions, including contract standards such as token standards (<a href="EIPS/eip-20">ERC20</a>), name registries (<a href="EIPS/eip-26">ERC26</a>, <a href="EIPS/eip-137">ERC137</a>), URI schemes (<a href="EIPS/eip-67">ERC67</a>), library/package formats (<a href="EIPS/eip-82">EIP82</a>), and wallet formats (<a href="EIPS/eip-75">EIP75</a>, <a href="EIPS/eip-85">EIP85</a>).</p>
|
||||
<p>Application-level standards and conventions, including contract standards such as token standards (<a href="EIPS/eip-20">ERC20</a>), name registries (<a href="EIPS/eip-137">ERC137</a>), URI schemes (<a href="EIPS/eip-681">ERC681</a>), library/package formats (<a href="EIPS/eip-190">EIP190</a>), and wallet formats (<a href="https://github.com/ethereum/EIPs/issues/85">EIP85</a>).</p>
|
||||
|
||||
<h3><a href="{{"informational"|relative_url}}">Informational</a> ({{site.pages|where:"type","Informational"|size}})</h3>
|
||||
<p>Describes a Ethereum design issue, or provides general guidelines or information to the Ethereum community, but does not propose a new feature. Informational EIPs do not necessarily represent Ethereum community consensus or a recommendation, so users and implementers are free to ignore Informational EIPs or follow their advice.</p>
|
||||
|
|
|
|||
Loading…
Reference in New Issue