Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing Draft or Last Call 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 or Last Call EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
* EIP-2364: eth/64: forkid-extended protocol handshake
* EIP-2364: fix review issues from Martin
Co-Authored-By: Martin Holst Swende <martin@swende.se>
* EIP-2364: Add reference to current eth/63 spec
Co-Authored-By: Alex Beregszaszi <alex@rtfs.hu>
* EIP-2364: Fix title to make the web generator happy
Co-Authored-By: Alex Beregszaszi <alex@rtfs.hu>
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing Draft or Last Call 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 or Last Call 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 or Last Call 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 or Last Call 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 or Last Call EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
Since the Istanbul meta-EIP has EIP-1108 listed for the hardfork and
the implementation tracker lists everyone as having merged, this EIP
seems reasonable to move to Final status.
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing Draft or Last Call EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
* Add Matomo tracking
* Add development instructions to README
* Add dynamic metadata for EIP pages
* Escape title strings
* Remove Matomo
* Use variables from _config.yaml in head.html
* Omit Jekyll version from header
* Also use twitter_username from _config.yml
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing Draft or Last Call 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 or Last Call 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 or Last Call 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 or Last Call 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 or Last Call EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing
* Add permissions system draft
* Fix typo, add missing link, one language change
**Previously:**
>Today web3 browsers like MetaMask always prompt on a per-action basis, but this maximizes security at the cost of user friction. An alternative model of security is to allow applications to request a series of permissions from a user at a time.
**Now:**
>Today web3 browsers like MetaMask always prompt on a per-action basis. This provides security at the cost of substantial user friction. We believe that a single permissions request can achieve the same level of security with vastly improved UX.
**Reasoning:** The former can be interpreted to imply that the permissions model is "less secure." The goal of the updated wording is to preclude that interpretation.
* Add link to active related issue
* Add discussions-to link
* Add header image for proposal
* Add note on domain string
* Update ocap-ld to new name zcap-ld
* Adopt EIP 2255 name
* Fixed spelling
* Fix validations
* First draft for ENS multicoin support
* Rewrite multicoin support to use maps
* Tweaks and fixes
* Update and rename eip-draft-ens-multicoin.md to eip-2304.md
Hi, I'm a bot! This change was automatically merged because:
- It only modifies existing Draft or Last Call 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 or Last Call EIP(s)
- The PR was approved or written by at least one author of each modified EIP
- The build is passing