EIP831 - URI Format for Ethereum, in Status

ricardo3 · October 10, 2019, 9:11pm

Topic to discuss about the proposal of adopt EIP831 for various use-cases inside Status, such as linking stuff inside status, as extensions, chat rooms, user profiles, bootnodes, and other.

Can be used in:

QRCode,
chat messages
dapps links
?

The way the elements inside of the ERC831 path described in the examples are up to improvement.

1. Profile link:

Only username (for stateofus.eth subnodes only):
ethereum:status-user@3esmit

Complete ens domains:
ethereum:[email protected]
ethereum:[email protected]

2. Public chat:

ethereum:status-chat#status-keycard

Public chat message permalink

Exclusively public chat messages can have a permalink which contains needed information to ask history nodes for the contents.
ethereum:status-chat#room#msgHash

3. Private message:

Optional, redundant to Profile link
Only username (for stateofus.eth subnodes only):
ethereum:status-chat@3esmit

Complete ens domains:
ethereum:[email protected]
ethereum:[email protected]

4. Group chat join key

Might not be applicable.
ethereum:status-chat#0xd4e56740f876aef8c010b86a40d5f56745a118d0906a34e69aec8c0db1cb8fa3

5. Watch token (by link)

ethereum:token-erc20:snt.thetoken.eth
ethereum:token-erc20:snt.thetoken.eth:SNT:Status Network Token:18
ethereum:token-er721:snt.thetoken.eth

6. Bootnodes

ethereum:status-bootnode:enode://e8a7c03b58911e98bbd66accb2a55d57683f35b23bf9dfca89e5e244eb5cc3f25018b4112db507faca34fb69ffb44b362f79eda97a669a8df29c72e654416784@47.91.224.35:30404

7. History nodes

ethereum:status-historynode:enode://da61e9eff86a56633b635f887d8b91e0ff5236bbc05b8169834292e92afb92929dcf6efdbf373a37903da8fe0384d5a0a8247e83f1ce211aa429200b6d28c548:[email protected]:30504

8. Status Extensions

current: status-im://extension/ipfs@QmV8JsEA2fBnjstH3MJzK5SgF9F7qNSyKLo2LapYia5pX4
proposed: ethereum:status-extension:ipfs@QmTeW79w7QQ6Npa3b1d5tANreCDxF2iDaAPsDvW6KtLmfB

github.com

status-im/status-mobile/blob/e7427997d253ed04e0c5f7044fbfefa24b31a7a8/doc/decisions/0002-extension-uri.md

# 0002. Extension URI

| Date | Tags |
|---|---|
| 2018-04-26 | extension, uri, ethereum |


## Status

proposed

## Context

Extensions are defined by an EDN file accessed from decentralized storage. An URI schema allows to identify those files.

## Decision

URI follows ethereum URI schema as specified in [EIP 831](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-831.md)

This file has been truncated. show original

9. web3 plugins

ethereum:plugin-ipfs@QmTeW79w7QQ6Npa3b1d5tANreCDxF2iDaAPsDvW6KtLmfB

10. other/more ?

What more we can permalink in status using EIP831?

frank · October 11, 2019, 7:41am

looks like status is ready to use ipfs as a hard dependency, currently the ipfs gateway is already blocked by China GFW, status mass adoption in China would be really hard…

ricardo3 · October 11, 2019, 10:10am

Hey, thanks for the details on China.

We don’t plan to use IPFS as a hard dependency. Here it was used just as example, but we should support also SWARM, or other that might appear.

What would you suggest as decentralized file storage that works in China?

frank · October 12, 2019, 1:42am

i don’t know, what i know is most of exposed public ipfs gateway has been blocked by GFW. it’s a big pressure as a software engineer, u can only access very limited resource without vpn…and most of normal Chinese don’t even know what vpn is

ricardo3 · October 12, 2019, 3:51am

Ahh, I see. It should be possible for china to run their own nodes, so it should be possible to use IPFS there, but not through a gateway.

The plan for web3 is to support multiple storage platforms: ERC-1577: contenthash field for ENS . I’ve seen DApps stored on IPFS, DApps using Swarm and even using DAT protocol ( GitHub - beakerbrowser/beaker: An experimental peer-to-peer Web browser )

Thats why extensions/plugins have defined what is the type storage used.