# URL/URI standard working group ## Meeting 6 **Date and Time**:Aug 08 at 17:00 UTC **Agenda**: https://github.com/ethereum-cat-herders/EIPIP/issues/165 **Recording**: ### Proposed next steps - Sam wilson will take a look at the [URL proposal](https://ethereum-magicians.org/t/idea-proposal-introducing/9906). - Ricardo will coordinate with Qi for Method Signature. - Merge future URI/URL meeting with Wallet Devs meeting. The next Wallet Devs Meeting is planned on Aug 17, 2022. ### Meeting summary 1. Idea for compact URL proposals - Trey added his thoughts [here](https://ethereum-magicians.org/t/idea-proposal-introducing/9906/7). - The proposal is in exploration (pre-`Draft`) phase - Inviting community to review 2. Progress on EIPs - [EIP-67](https://github.com/ethereum/EIPs/pull/5338) - PR is Merged and the proposal is added as `Withdrawan`. Authors of proposal having dependency on EIP-67 may now proceed without any blocker. - EIP-2400: URL Format for Transaction Receipts - Currently in `Review` status, EIP is making progress.Sam recommended to coordinate for method signature with author of EIP-4804. - EIP-4804: Web3 URL to EVM Call Message Translation - In `Review` status. The general format of URI needs to be defined. 3. Merging URI/URL meeting with Wallet Devs meeting - Proposed by Pooja R. to merge this meeting with Wallet Dev meeting led by Sam Wilson. - Wallet devs meeting has a decent number of participation from infra providers and it will only make sense to collect feedback from the community who is going to be the implementers of these EIPs. - The next meeting is planned on Aug 17th. Reach out to Sam Wilson to join the Discord. ### Participants - Ricardo - Sam Wilson - Trey - Qi - Pooja Ranjan ## Meeting 5 **Date and Time**: July 25, 2022 at 17:00 UTC **Agenda**: https://github.com/ethereum-cat-herders/EIPIP/issues/159 **Recording**: https://hackmd.io/@poojaranjan/URLWorkingGroup#Meeting-5 ### Proposed next steps * Sam & Ligi will work on moving EIP-831 towards `Final`. * Rocardo will update EIP-2400 to add EIP-831 and continue collecting feedback for next few days before moving to the `Last Call`. * Trey will write up a draft spec not as an EIp, but to get some ideas of what should be included in the more conserved version of this. Extensions will be more useful to have later on. He will share the link on the ECH Discord for feedback. ### Meeting summary #### 1. Replace EIP-831 with a new EIP that will handle ethereum[-]: namespace, and also propose a shortcut eth[-]: - Recap of the last meeting - 2 PRs - [5335](https://github.com/ethereum/EIPs/pull/5335) & [5338](https://github.com/ethereum/EIPs/pull/5338) are added to EIPs GitHub in the past 24 hrs in relation to [EIP-831](https://eips.ethereum.org/EIPS/eip-831). - Ligi, the author of EIP-831 joined the meeting and is willing to resurrect the EIP-831 with [PR-5335](https://github.com/ethereum/EIPs/pull/5335) and will like to mention EIP-67, which currently isn't availabel in the GitHub repository. - Sam Wilson created [PR-5338](https://github.com/ethereum/EIPs/pull/5338) to create an EIP (with Alex Van de Sande (@alexvandesande) as the author) and move EIP-67 to `Withdrawn`. #### 2. Progress on "Idea for compact URL proposals" * Trey provided update on the [discussion thread at FEM](https://ethereum-magicians.org/t/idea-proposal-introducing/9906) to collect feedback on compact URL proposals. #### 3. Progress on EIPs A. EIP-2400: URL Format for Transaction Receipts - EIP is in `Review`. Author will make some more changes. B. EIP-4804: Web3 URL to EVM Call Message Translation - Responded to comments on ambiguity and other questions Qn.: Is there any reason to not make 831 style. Ans: It is possible changing schema prefix. #### EIP Review process - Will there be any reviewer to step in? - `Review` status is a formal signal to the ecosystem that you are not expecting to change the EIP. - There will not be any assigned reviewer. - People in the meeting will probably be the people to review. - May also be discussed in EIP editors apprenticeship meeting. **Announcement** - Next Wallet dev meeting is planned on July 27th at 12:30 pm Eastern time. - Next URL/URI standard working group meeting is planned on **Aug 08 at 17:00 UTC**. ### Links shared during the call: - https://github.com/ethereum/EIPs/pull/5335 - https://github.com/ethereum/EIPs/pull/5338 - https://ethereum-magicians.org/t/idea-proposal-introducing/9906 ### Participants - Ligi - Ricardo - Sam Wilson - Trey - Qi - Pooja ## Meeting 4 **Date**: July 11, 2022 **Agenda**: https://github.com/ethereum-cat-herders/EIPIP/issues/149 **Recording**: https://youtu.be/NaJPBLmu0UU **Zoom Chat**: https://us02web.zoom.us/rec/sdownload/gl5QNgxWGRNWHXTqDRu6Zc3XQfDqqfUyAxDLZRbLisCtHpJ8dcar3hDxgTvj0EiTxuCkQKVDNeyaras-.1n66EtxokyQwdQW_ Passcode: *py9fA4? ### Proposed next steps - Ricardo will make a pull request to move the EIP-2400 from `Stagnant` to `Review` to collect more review comments and feedbacks from the community. - Qi will make a [pull request](https://github.com/ethereum/EIPs/pull/5218) to move the EIP-4804 from `Draft` to `Review` to collect more review comments, feedbacks from the community and update progress in the next call. - Luc will create a [discussion thread at FEM](https://ethereum-magicians.org/t/idea-proposal-introducing/9906) to collect feedback on compact URL proposals. ### Meeting summary - Trey shared his [pov](https://0x0.st/oMwR.txt) to have higher level specification for standerdization. - Mixed response; pasrt of it will be further discussed [here](https://ethereum-magicians.org/t/idea-proposal-introducing/9906). - Ricardo (author of EIP-2400) seems to have agreed for a compact proposal, a better proposal. Specs not clear enough. Discussion will be continued in the next meeting - Qi share a [comprehensive introduction to EIP-4804](https://docs.google.com/presentation/d/1rYnkPZ65XuSauZQr77_08-Vj770-Hc5fvWvTT0K-tpQ/edit?usp=sharing) including background, motivation, and applications, and share some changes to discuss. - Received mixed response, unclear of project support. - Author will move the proposal to `Review`. - The feedback received in earlier meetings: - Decide on a different schema (web3q for ex) - Identity is inside of URL, cannot exist, origin doesnt/couldnt/shouldnt know - URL uses "methodId" .. which doesnt exist, unless we query etherscan specifically and the contract is verified - Arguments cant be sent with splitting - Ambiguous argument input - Ambiguous argument types with too large room of interpretation Response shared by Qi [here](https://discord.com/channels/916516304972824576/916713912970412103/996142026863149217). ### Links shared during the call: * https://github.com/ethereum-cat-herders/EIPIP/issues/149 * https://github.com/ethereum/EIPs/issues/719 * https://github.com/brunobar79/eth-url-parser/pull/12 * https://github.com/lucemans/eth-url-parser/tree/multi * https://github.com/lightning/bolts/blob/master/11-payment-encoding.md * https://www.geeksforgeeks.org/difference-between-json-and-bson/ * https://eips.ethereum.org/EIPS/eip-681 * https://github.com/ethereum/EIPs/pull/5217 * https://ethereum-magicians.org/t/idea-proposal-introducing/9906 ### Participants - Luc - Pooja Ranjan - Qi Zhou - Micah Zoltu - Ricardo Schmidt - Lightclient - Trey - Helgesson - Victor Zhou ## Meeting 3 **Date**: June 20, 2022 **Recording**:https://youtu.be/83ZY5qrU5M4 ### Proposed next steps - EIP-4804: - Author may reach out projects for support and wider adoption. - May also reach [CAIP](https://github.com/ChainAgnostic/CAIPs) group for support - **Next meeting**: July 11, 2022 at 17:00 UTC - Create agenda and share ### Summary from the meeting - Qi explained the EIP with a slides presentation - Qn by Greg: what is the biggest benefit that by this proposal?What is the main problem that you are trying to solve? - Is it access to dApp? - Is it for coding data or - for both? What is the use of data? ### Links shared in the meeting - https://github.com/ChainAgnostic/CAIPs ## Meeting 2 **Date**: June 06, 2022 **Recording**: https://youtu.be/8kredlTraAg ### Proposed next steps * EIP-4804 - Author will try to incorporate suggestions shared in the meeting and update. * EIP-2400 - Author will revisit the proposal and will make pull request to bring the proposal to `Review` and work towards moving the proposal to `Final`. * Sam Wilson will try to have a RPC endpoint standard. * Reach out wallet devs and try to have them on the call for the next meeting. #### From ECH Discord [Comments on the URL/URL proposals](https://discord.com/channels/916516304972824576/916713912970412103/984312506728206386) from Discord user treyzania - https://0x0.st/oMwR.txt [![](https://i.imgur.com/9El8zoI.png)](https://discord.com/channels/916516304972824576/916713912970412103/984149960935231548) ### Links shared in the meeting * https://hackmd.io/@poojaranjan/URLWorkingGroup * https://gitcoin.co/grants/4679/web3q-an-end-to-end-fully-decentralized-web-proto * https://eips.ethereum.org/EIPS/eip-2400 **Zoom chat** - https://us02web.zoom.us/rec/sdownload/6ibNESQeQvoK2KSun-WSht_CW8QzW2XMKVXvVn3sO4_mhPgSeexYUWMS4Y03oUlSzYMRuRSF7rKg_Fmb.Ui6t9TodzX6J_Fuv Passcode: hfjx%1^Z **Next meeting**: June 20, 2022 ## Meeting 1 **Date**: May 23, 2022 **Recording**: https://youtu.be/wy1NaVFrhsk ### Proposed next steps - Talk to wallets about supporting RPC & considering supporting some type of RPC lists. - Do some work on transfer or remove the RPC endpoint to add new RPC to wallets. ### Links shared in the meeting * https://github.com/ethereum/EIPs/pull/5094 * https://galileo.web3q.io/ensdomains.eth:4/ * https://eips.ethereum.org/EIPS/eip-3085 * https://eips.ethereum.org/EIPS/eip-4804 **Next meeting**: June 06, 2022 --- ## Goal A common proposal for URL/URI Ethereum Standard (with a combination of different proposals) that is really solid and could be pushed towards `Final` status for application developers to simply adopt it. ### Why a working group? [EIP GitHub repository](https://github.com/ethereum/EIPs) has received multiple proposals related to URL/URI standards. Some of them are `Stagnant` or in any other status, only one reached `Final`. A few proposals are overlapping, too. In [EIPIP meeting 56](https://www.youtube.com/watch?v=IhYm5Bhxm4U&t=2491s), it was proposed by one of the EIP editors, Matt Garnett, to have a working group to maybe bring all authors together to work towards pushing an Ethereum Standard. ### What are existing proposals? | Proposal | Example | Author(s) | EIP-status | | -------- | ------- | -------- | -------- | |[EIP-681: URL Format for Transaction Requests](https://eips.ethereum.org/EIPS/eip-681) | `ethereum:0x8...7/transfer?address=0x8...2&uint256=1` | Daniel A. Nagy |`Final`| | [EIP-831: URI Format for Ethereum](https://eips.ethereum.org/EIPS/eip-831) | `ethereum:foo-0x1..F` | ligi | `Stagnant` | |[EIP-1328: WalletConnect Standard URI Format](https://eips.ethereum.org/EIPS/eip-1328) | `wc:8...c-0000-0000-0000-0...0@1?bridge=https%3A%2F%2Fbridge.walletconnect.org&key=4...a` | ligi, Pedro Gomes |`Stagnant` | |[EIP-1710: URL Format for Web3 Browsers](https://eips.ethereum.org/EIPS/eip-1710)| `dapp:1@peepeth.com/brunobar79` | Bruno Barbieri |`Stagnant` | | [EIP-2400: URL Format for Transaction Receipts](https://eips.ethereum.org/EIPS/eip-2400) | `ethereum:tx-` | Ricardo Guilherme Schmidt, Eric Dvorsak |`Stagnant`| |[EIP-2942: EthPM URI Specification](https://eips.ethereum.org/EIPS/eip-2942) | `ethpm:` | Nick Gheorghita, Piper Merriam, g. nicholas d'andrea, Benjamin Hauser |`Stagnant` | |[EIP-4804: Web3 URL to EVM Call Message Translation](https://eips.ethereum.org/EIPS/eip-4804) |`web3://ensdomains.eth:4/` | Qi Zhou, Chao Pi, Sam Wilson|`Draft`| |[PR-5094: URI Format for Ethereum Network Switching](https://eips.ethereum.org/EIPS/eip-5094) | |lucemans | `WIP`| ### Usage for current Schemes | scheme | Usage | | -------- | ----- | | ethereum | Request Payment, View Transaction, Add Network | | dapp | Generic Dapp URLs for use with deeplinking to wallets | | wc | Wallet Connect | | ethpm | Ethereum Package Manager | ### How do we propose to proceed? Matt Garnett [suggested](https://github.com/ethereum-cat-herders/EIPIP/issues/136#issuecomment-1130070394) looking for someone to lead the URL standard for chain working group. The lead is expected - to get the authors of the other proposed standards on a call, - sketch out what their goals are, - combine their efforts into a single "blessed" standard.