* Formalize IPFS hash into ENS(Ethereum Name Service) resolver
* Update and rename eip-X.md to eip-1062.md
* Remove superfluous space after 'category'
* Update the URL for discussion
* Fix typos
* Fix typo
* Update Specification, Rationale and Test Cases
* Store multihash value in bytes
* Add initial EIP skeleton
* Initial take through "Rationale"
* First very rough draft of ERC20 Metadata Extension
Nearly ready for comments by Matt, Matt, and John
* Initial "Token Metadata Standard" Proposal + small change to ERC721
- Added initial “Token Metadata JSON Schema”
- Re-named “ERC721 Metadata JSON Schema” to “Token Metadata JSON
Schema” in the ERC721 EIP
* ERC20 Metadata Extension ready to read
* Update Title of ERC Metadata Extension
* Fixing Matt's Github handle
Apparently Github handles for authors are meant to be “accurate” - who
knew?
* update grammatical errors; properly format JSON to remove excess commas
* update JSON descriptions & make grammatical changes to EIP
* Changed language in Token Metadata JSON Schema to reflect use by tokens which are not NFT's. Added clarification for backwards compatibility
* update authors and contact email
* Author Fix
* Removing ERC20 Metadata Extension
This branch is going to be just the Token Metadata Standard
* Removing change to 721 and renaming to 1047
* Full ERC721 revert
No changes to ERC721 in this PR
* Add initial EIP skeleton
* Initial take through "Rationale"
* First very rough draft of ERC20 Metadata Extension
Nearly ready for comments by Matt, Matt, and John
* Initial "Token Metadata Standard" Proposal + small change to ERC721
- Added initial “Token Metadata JSON Schema”
- Re-named “ERC721 Metadata JSON Schema” to “Token Metadata JSON
Schema” in the ERC721 EIP
* ERC20 Metadata Extension ready to read
* Update Title of ERC Metadata Extension
* Fixing Matt's Github handle
Apparently Github handles for authors are meant to be “accurate” - who
knew?
* update grammatical errors; properly format JSON to remove excess commas
* update JSON descriptions & make grammatical changes to EIP
* Changed language in Token Metadata JSON Schema to reflect use by tokens which are not NFT's. Added clarification for backwards compatibility
* update authors and contact email
* Author Fix
* Removing Token Metadata Standard
This Branch will be just the ERC20 Token Metadata Extension
* Updates from reviewer comments
- Some grammar fixes
- Removed mentions of ERC721 standard code
- Added EIP # and discussion forum
* Fixing discussion-to
discussion-to instead of discussion-forum
* Should remove the change to 721
* 100% revert on ERC721
No changes to ERC721 in this PR now
* Discussions-to
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
* Update and rename EIP-X-authorisations-nickjohnson.md to eip-927.md
* Update and rename EIP-X-metadata-nickjohnson.md to eip-926.md
* Update eip-927.md
This change makes information in ENR compatible with the existing
discovery protocol:
- The default identity scheme is now called "v4" to make the name shorter.
- Node addresses are derived as the hash of the uncompressed public key.
- The "ip4" and "ip6" keys are merged into a single "ip" key which
can hold a IPv4 or IPv6 address.
- The "discv5" key is now called "udp".
- The new "tcp" key holds the TCP port.
* epi drafted
* minor changes made
* minor changes made
* changes to sender interface and added diagrams
* added diagrams in the markdown
* updated the diagrams
* update the headers
* made changes suggested by @arachnid
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
* Create EIP-X-on-chain-issuance-control.md
* Update and rename EIP-X-on-chain-issuance-control.md to EIP-1000-on-chain-issuance-control.md
* Update and rename EIP-1000-on-chain-issuance-control.md to EIP-1015-on-chain-issuance-control.md
* Rename EIP-1015-on-chain-issuance-control.md to EIP-1015.md
* Rename EIP-1015.md to eip-1015.md
* Create eip-541.md
* Added proofOfWork and getDifficultyAdjustmentPeriod
* Updated EIP number
Updated EIP number to reflect PR
* Several functional updates
Upon review from a wider audience, this commit includes an interface definition of minimum functionality for mined tokens, a more comprehensive abstract contract that defines required behavior for 4 separate internal phases of solution verification, difficulty modification, epoch period updates, and token reward. Additionally added an example mining program and several simple and complex examples are referenced. Included main net deployed implementation contract addresses 0xbitcoin and PoWAdv. Updated new header format per EIP standardization.
* Attempt at format fix
trying to address :
Incremental build: disabled. Enable with --incremental
Generating...
Liquid Exception: Liquid error (/home/travis/build/ethereum/EIPs/_includes/eiptable.html line 11): comparison of Array with Array failed included in all.html
jekyll 3.6.2 | Error: Liquid error (/home/travis/build/ethereum/EIPs/_includes/eiptable.html line 11): comparison of Array with Array failed included
The command "bash -ex .travis-ci.sh" exited with 1.
* Abstract contract update
Added full Mineable Abstract contract code to illustrate a more behaviourally specific implementation to the relatively general EIP918 interface.
* init
* permissions init
* start of permissions service
* Token Validator (#6)
* File naming convention
* Remove previous versions
* remove reference to the old variable
* Update frontmatter as per @Arachnid
* Switch to byte
* EIP-1 minors edits: clarify some sections on EIP collaborators and editors, cross-links, links, grammar, etc.
* Add a link for [Ethereum philosophy](https://github.com/ethereum/wiki/wiki/White-Paper#philosophy) to the section in the white paper that was originally removed and which I re-added recently.
* Revise the format for the author header (names can be optional for anonymity).
* History edits (link to revision history + a minor edit).
* Add cross-links to other sections for better readability and clarity.
* Add clarifications on approval before merging from both editors and authors.
* Add more links for discussion channels
* Link to other clients and eips.ethereum.org.
* Reorder EIP editors roughly based on recent contributions.
* Other minor edits: grammar, etc.
* Add a link to core dev meetings
* discussion*s*
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
* correct precompile address; expand on motivation; add links to implementation PRs
* return length is 4 octets, not 1; more text polish
* typo
* expand implementation section; add link to cpp-ethereum PR
* Create blockhash_refactoring.md
Stores blockhashes in the state, reducing the protocol complexity and the need for client implementation complexity in order to process the BLOCKHASH opcode. Also extends the range of how far back blockhash checking can go, with the side effect of creating direct links between blocks with very distant block numbers, facilitating much more efficient initial light client syncing.
* Update blockhash_refactoring.md
* Update blockhash_refactoring.md
* Update blockhash_refactoring.md
* Update blockhash_refactoring.md
* Update blockhash_refactoring.md
* Update blockhash_refactoring.md
* Update blockhash_refactoring.md
* Update blockhash_refactoring.md
* Update blockhash_refactoring.md
* Update blockhash_refactoring.md
* Rename blockhash_refactoring.md to eip-210.md
* Create eip-draft_uniformity_between_0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B_and_0x15E55EF43efA8348dDaeAa455F16C43B64917e3c.md
* Fix typo
* Use pull request ID as tentative EIP
I think this might fix the Travis CI build errors
* Update and rename eip-draft_uniformity_between_0xAb5801a7D398351b8bE11C439e05C5B3259aeC9B_and_0x15E55EF43efA8348dDaeAa455F16C43B64917e3c.md to eip-1010.md
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
* Claim a random number
* Add specification
* Add rationale
* Improve wording
* Improve formatting
* Improve wording
* Specify the account values for balance, nonce, code, and storage
* Be more specific about a hard-fork
* Add poc implementation for Parity
* Improve formatting
* Improve formatting
* Make sure the total supply will be unchanged.
* Point to relevant changes in chain spec.
* Remove contracts/#74 code from the proposal.
* Use the old but patched library
* Highlight differences to the initially deployed contract
* Add code and storage for the stateDiff
* Update resources
* Update resources
* Add correct discussion URL
* Standard Track -> Standards Track
* Link the PR for Parity
* Rationale on unchanged Ether supply
* Split specification alternatives via bytecode vs. codehash
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
* Add Github usernames
* Remove about.me link from triangular brackets
* Add @ before usernames, also note the previous commit was adding content from the original PR.
#908
* parentheses instead of triangular brackets: (@Githubusername)
* replace and with ,
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
* Create eip-Reward-full-nodes-validating-tx.md
* Update eip-Reward-full-nodes-validating-tx.md
* Update eip-Reward-full-nodes-validating-tx.md
* Update eip-Reward-full-nodes-validating-tx.md
* Update eip-Reward-full-nodes-validating-tx.md
* Update eip-Reward-full-nodes-validating-tx.md
* Update eip-Reward-full-nodes-validating-tx.md
* Update eip-Reward-full-nodes-validating-tx.md
* Update eip-Reward-full-nodes-validating-tx.md
* Update eip-Reward-full-nodes-validating-tx.md
* Update eip-Reward-full-nodes-validating-tx.md
* Update and rename eip-Reward-full-nodes-validating-tx.md to eip-Reward-full-nodes-and-clients.md
* Update eip-Reward-full-nodes-and-clients.md
* Update eip-Reward-full-nodes-and-clients.md
* Update eip-Reward-full-nodes-and-clients.md
* Update eip-Reward-full-nodes-and-clients.md
* Update eip-Reward-full-nodes-and-clients.md
* Update eip-Reward-full-nodes-and-clients.md
* Quotes for Micah
* The amount of computation to validate a transaction will be the same as a miner...
* Add comments on Micah's suggestions and give further specification details
* Further commentary on transaction fee amount for full nodes vs miner tx fees
* Add "One problem with this is that a miner could run a full node validator using a different address with the same computer, and just cache the result of their execution and use it for the full node validator. I'm not sure how you would prevent this, but perhaps you could using IP address tracking (similarly asserting that the IP address of a full node validator isn't the same as the miner) which would add additional complexity to the protocol, but this could also be hacked with dynamic IPs and VPNs."
* he user agent would contain the information needed to send an amount of ETH to the full node and the client, which are the addresses of these parties and the amounts to add. I think full nodes would need to add to their set up to add the address to receive ETH after validating transactions. These fields could be read-only, or immutable, so that someone can't overwrite them with another address, thus preventing one possible attack.
* Add a missing T
* Update frontmatter
* Comment out implementation, add backwards incompatibility
* Update the specification, rewording and moving content
* Update the header, Test Cases and Implementation
* Update eip-Reward-full-nodes-and-clients.md
* Chamge the category to Core
* to be assigned => <to be assigned>
* discussions-to: https://gitter.im/ethereum/topics/topic/5ac8574227c509a774e7901a/eip-reward-full-nodes-and-clients
* Move around fields in the header
* Add an extra line to see if that will get the build to pass
* Assign eip number 908
* Rename eip-Reward-full-nodes-and-clients.md to eip-908.md
* ERC777 A New Advanced Token Standard
* ERC777: Add ERC777 Logo
* ERC777: Normalize EIP/ERC names
* ERC777: Spec for tokensToSend when burning tokens
* ERC777: Update official repository
* ERC777: Clarification and corrections
- Clarify unclear sections of the spec
- Fix typos and grammar mistakes
- Improve aesthetics of the text
* ERC777: Change terminology of the repo, small fix
- Don't refer to the repo as the official repo but the repo of the
reference implementation
- Fix a small typo in the AuthorizedOperator event
* ERC777: logo & release to public domain (CC0)
* ERC777: Use markdown not html & relative links
* ERC777: Adapt to new EIP template
* ERC777: Use solidity syntax and fix relative links
* ERC777: Add discussions-to link
* ERC777: Fix link in discussion-to
* ERC777: Fix image links
* ERC777: Fix eip type
* ERC777: Update header
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
* ERC-820 Pseudo-introspection using a registry contract.
* Typos, links, and better explanation of Nicks deployment method
* Formating fix
* Email address
* solidity syntax highlight
* Adapt to new template for EIPs
* Discussions link added
* Fix link in discussion-to
* Type fixed
- Create `assets` folder
- Move existing EIPs (1, 107, 858) assets into the `assets` folder
- Update link to assets in EIPs 1, 107 and 858
- Describe the inclusion of assets for EIPs in `README.md`
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing draft EIP(s)
- The creator of this PR is listed as an author on all modified EIP(s)
- The build is passing
* Added initial ASIC-resistant EIP details
* Format fixed
* Format fixed
* Format fixed
* Format fixed
* Format fixed
* Grammar fixes
* Added mention of more invasive hash algorithm replacements
* Added mention of the single duplicate in 0x010001cf
* Adjusted language to remove speculation and focus on the purpose and motivation of this pull request
* Assigned EIP number and discussion URL, altered language to be more descriptive about the intention and risk. Removed unneeded Concensus/Block field changes.
* Clarified FNV rational, provided code for basic sanity FNV candidate analysis and FNV selection, grammar fixes
* initial submission of draft EIP for consideration
* EIP-884 correct spelling and add section on permissions management
* EIP-884 added oldHash
* EIP-884 changed getHash to hasHash and cleaned up grammar and spelling
* EIP-884 updates to wording
* EIR-884 added clarification on Delaware GCL vs Reg A+
* EIR-884 tweaks so the proposed code actually compiles
* EIP-884 simplified ownerAt and added requirement that a verified address that owns tokens can not be removed
* EIP-884 added link to reference implementation
* EIP-884 added notes on ERC721
* EIP-884 renamed document, removed references to Reg A+, and updated interface to include stock cancellation and reissuance.
* EIP-884 updated some documentation in the proposed interface
* EIP-884 added isHolder function to proposed interface
* EIP-884 moved to new frontmatter format
* EIP-884 removed 'requires' from metadata
* EIP-884 renamed file to match others
* Update social includes to link to repo, not org
* Add support for eip_validator by Makoto Inoue
* Fix external links in EIPs
* Change eip_validator to 0.3.0
* Fix dependency issues
* Update eip_validator to 0.3.4
* Add more condition on EIP input files
* Bump eip_validator to ignore invalid eip file format
* Fix EIP 86
- Fixed typo (operator to operators)
- Explicitly call out the implementation MUST support multiple operators per owner as implied by the comments
- Removed unnecessary throw from the dev instructions on setApprovalForAll
* Create abstraction.md
Implements a set of changes that serve the combined purpose of "abstracting out" signature verification and nonce checking, allowing users to create "account contracts" that perform any desired signature/nonce checks instead of using the mechanism that is currently hard-coded into transaction processing.
* Update abstraction.md
* Update abstraction.md
* Update abstraction.md
* Update abstraction.md
* Update abstraction.md
* Update abstraction.md
* Update abstraction.md
* Rename abstraction.md to eip-86.md, add copyright clause, fix header.
I'm adding myself as an co-author of this EIP. Nick and Maurelian can vouch that I wrote a large part of this text and helped design the initial mechanisms