-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Resurrect EIP-1328 #4416
Resurrect EIP-1328 #4416
Conversation
All tests passed; auto-merging...(pass) eip-1328.md
|
Seconded! We should also update the spec with parameters for v1.0 and v2.0 |
I think you can bring it to |
@axic thanks - but according to this state-transition diagram I cannot: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update this to the current EIP-1 standards:
- Add
description:
preamble and removeSimple Summary
- Optionally add
Motivation
- Remove
References
- Add
Backwards Compatibility
- Add
Security Considerations
- Make sure at least one author has a GitHub handle and not an email
Good catch. I think this is somewhat inconsistent, given if you have caught the bot at the time of making the change, you wouldn't need to do two steps. @MicahZoltu @lightclient do you want to enforce having two PRs here to first move to Draft then to Review? 😉 |
I actually caught it the first time: #4020 (comment) Do we really need to add empty sections for backward compatibility and security considerations when they do not apply? |
It seems so. |
I believe we discussed this and agreed that if the author wants to go from stagnant to Review that is fine. The Backward Compatibility and Security Consideration sections are required. At the least they should have a one-line blurb that says "There are no known backward compatibility issues introduced by this EIP" or "There are no known security issues presented by the introduction of this EIP." |
Bumping as this is heavily used in WalletConnect and it would be great to move to final |
can also be for desktop - maybe we should remove the whole part - because now there is also "copy" - no real value added anyway IMHO
## Abstract | ||
|
||
This standard defines how the data to connect some application and a wallet can be encoded with a URI. This URI can then be shown either as a QR code or for mobile to mobile as a link. | ||
This standard defines how the data to connect some application and a wallet can be encoded with a URI. This URI can then be shown either as a QR code or as a link. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pedrouid do we perhaps want to remove "This URI can then be shown either as a QR code or as a link." - think it adds no value and restricts us without a need. e.g. how does the "copy" fall in place there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like this is already addressed when "link" is mentioned since it's a common pattern to include copy to clipboard
for website links as well
Thanks @ligi for resurrecting this EIP. I will look into this by Tuesday to include the missing sections and parameters for v2.0 |
Sorry for the delay.... I have created a PR to Ligi's PR to include the v2.0 parameters: ligi#2 |
Incorporated most things requested - but have one open discussion point with @pedrouid - marking as draft until this is resolved. |
EIPS/eip-1328.md
Outdated
eip: 1328 | ||
title: WalletConnect Standard URI Format | ||
author: ligi <ligi@ligi.de>, Pedro Gomes <pedrouid@protonmail.com> | ||
author: ligi <@ligi>, Pedro Gomes <@pedrouid> | ||
type: Standards Track | ||
category: ERC | ||
status: Stagnant | ||
status: Draft | ||
created: 2018-08-15 | ||
discussions-to: https://ethereum-magicians.org/t/wallet-connect-eip/850 | ||
description: Standard for WalletConnect URIs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
eip: 1328 | |
title: WalletConnect Standard URI Format | |
author: ligi <ligi@ligi.de>, Pedro Gomes <pedrouid@protonmail.com> | |
author: ligi <@ligi>, Pedro Gomes <@pedrouid> | |
type: Standards Track | |
category: ERC | |
status: Stagnant | |
status: Draft | |
created: 2018-08-15 | |
discussions-to: https://ethereum-magicians.org/t/wallet-connect-eip/850 | |
description: Standard for WalletConnect URIs | |
eip: 1328 | |
title: WalletConnect Standard URI Format | |
description: Standard for WalletConnect URIs | |
author: ligi (@ligi), Pedro Gomes (@pedrouid) | |
discussions-to: https://ethereum-magicians.org/t/wallet-connect-eip/850 | |
status: Draft | |
type: Standards Track | |
category: ERC | |
created: 2018-08-15 |
Fixes field ordering to align with https://raw.githubusercontent.com/ethereum/EIPs/master/eip-template.md.
Also fixes ()
for GitHub username, <>
is for email.
Update eip-1328.md
@pedrouid thanks for the final changes for WC2.0! Think this one should be mergeable now. |
@SamWilsn @lightclient @axic This has been sitting waiting for a review for quite a while. Any chance one of you have some time to take a look? |
EIPS/eip-1328.md
Outdated
@@ -1,21 +1,18 @@ | |||
--- | |||
eip: 1328 | |||
title: WalletConnect Standard URI Format |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
title: WalletConnect Standard URI Format | |
title: WalletConnect URI Format |
EIPS/eip-1328.md
Outdated
@@ -1,21 +1,18 @@ | |||
--- | |||
eip: 1328 | |||
title: WalletConnect Standard URI Format | |||
author: ligi <ligi@ligi.de>, Pedro Gomes <pedrouid@protonmail.com> | |||
description: Standard for WalletConnect URIs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
description: Standard for WalletConnect URIs | |
description: Define URIs for initiating connections between applications and wallets |
EIPS/eip-1328.md
Outdated
## Rationale | ||
|
||
The need for this ERC stems from the discussion to move away from JSON format used in the alpha version of the WalletConnect protocol which makes for very inneficient parsing of the intent of the QR code, making it easier to create better QR code parsers APIs for Wallets to implement. Also by using a URI instead of a JSON inside the QR-Code the Android Intent system can be leveraged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This "Rationale" section reads more like it should belong in the "Motivation" section.
"Motivation" explains why the EIP as a whole needs to exist, while "Rationale" should explain individual choices made in the EIP itself.
Opened ligi#5 with my suggestions. |
Apply my suggestions to the PR
merged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we're good to go!
@ligi is this good to go to review? |
yes! |
* Resurrect EIP-1328 * Update to current EIP-1 * Remove the specific use case can also be for desktop - maybe we should remove the whole part - because now there is also "copy" - no real value added anyway IMHO * Update eip-1328.md * Update eip-1328.md * Update EIPS/eip-1328.md * Update EIPS/eip-1328.md * Update EIPS/eip-1328.md * Update EIPS/eip-1328.md * Update eip-1328.md * Apply suggestions by @MicahZoltu * Apply my suggestions to the PR Co-authored-by: Pedro Gomes <pedrogomes94@gmail.com> Co-authored-by: Sam Wilson <sam.wilson@mesh.xyz>
* Resurrect EIP-1328 * Update to current EIP-1 * Remove the specific use case can also be for desktop - maybe we should remove the whole part - because now there is also "copy" - no real value added anyway IMHO * Update eip-1328.md * Update eip-1328.md * Update EIPS/eip-1328.md * Update EIPS/eip-1328.md * Update EIPS/eip-1328.md * Update EIPS/eip-1328.md * Update eip-1328.md * Apply suggestions by @MicahZoltu * Apply my suggestions to the PR Co-authored-by: Pedro Gomes <pedrogomes94@gmail.com> Co-authored-by: Sam Wilson <sam.wilson@mesh.xyz>
EIP-1328 is heavily used in WalletConnect - and very unlikely to change - but as I understand the process we now need to move it to Draft then to Review then to Last Call then to Final. Starting this process now - cc @pedrouid