Skip to content
New issue

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

EIP 2255: Web3 Wallet Permissions System #2302

Merged
merged 12 commits into from
Oct 2, 2019
Merged

EIP 2255: Web3 Wallet Permissions System #2302

merged 12 commits into from
Oct 2, 2019

Conversation

danfinlay
Copy link
Contributor

@danfinlay danfinlay commented Sep 30, 2019

As up for discussion on ethereum-magicians.

danfinlay and others added 9 commits August 22, 2019 12:49
**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.
Fix typo, add missing link, one language change
@danfinlay danfinlay changed the title Wallet permissions EIP 2255: Web3 Wallet Permissions System Oct 1, 2019
@Arachnid Arachnid merged commit d041066 into ethereum:master Oct 2, 2019
@danfinlay
Copy link
Contributor Author

Thanks!!

ilanolkies pushed a commit to ilanolkies/EIPs that referenced this pull request Nov 12, 2019
* 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
MadeofTin pushed a commit to MadeofTin/EIPs that referenced this pull request Nov 13, 2019
* 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
tkstanczak pushed a commit to tkstanczak/EIPs that referenced this pull request Nov 7, 2020
* 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
Arachnid pushed a commit to Arachnid/EIPs that referenced this pull request Mar 6, 2021
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants