Skip to content

Latest commit

 

History

History
28 lines (19 loc) · 2.22 KB

base.md

File metadata and controls

28 lines (19 loc) · 2.22 KB
Raw

Basic structure

Base structure

web3://<contract>[:<chainId>]/<path>

The URLs are following a structure close to traditional HTTP URLs:

  • <contract> can either be an contract address such as 0x5ad14e8439b9619e165db27545faf6df13e2b947 or a domain name such as web3url.eth. Learn more about domain name resolution.
  • chainId is optional and indicate the chain id of the blockchain where to query the smart contract. web3://0x5a985f13345e820aa9618826b85f74c3986e1463:5/tokenHTML/2 will for example query on the goerli blockchain (chain id = 5).
  • path follows a similar structure than traditional HTTP URLs, in the form of /path/path2?query1=xx&query2=xx. To know how to build a path, we first need to know the resolve mode of the called smart contract

Standards

🟠 The web3:// protocol is made of various Ethereum ERCs, some of which are still in draft status. We will flag on this documentation what is definitive and what could change.

Here is the list of ERCs :

  • ERC-4804: The base ERC from which everything is based on. This ERC is final and cannot be edited anymore.
  • ERC-6860: (Draft) This ERC updates the base ERC-4804 with clarifications, minor fixes and changes. Still in draft status.
  • ERC-6821: (Draft) ENS resolution : support for the contentcontract TXT field to point to a contract in another chain. Still in draft status.
  • ERC-6944: (Draft) New resolve mode offloading some parsing processing on the browser side, based on ERC-5219. Still in draft status.
  • ERC-7087 : (Draft) Auto mode : Add MIME type support. Still in draft status.
  • ERC-7617 : (Draft) Add chunk support in ERC-6944 resource request mode. Still in pending merge status.
  • ERC-7618 : (Draft) Add Content-encoding handling in ERC-6944 resource request mode. Still in pending merge status.