Alert Source Discuss
⚠️ Draft Standards Track: ERC

ERC-7572: Contract-level metadata via `contractURI()`

Specifying and updating contract-level metadata

Authors Devin Finzer (@dfinzer), Alex Atallah (@alexanderatallah), Ryan Ghods (@ryanio)
Created 2023-12-06
Discussion Link https://ethereum-magicians.org/t/erc-contract-level-metadata-via-contracturi/17157

Abstract

This specification standardizes contractURI() to return contract-level metadata. This is useful for dapps and offchain indexers to show rich information about a contract, such as its name, description and image, without specifying it manually or individually for each dapp.

Motivation

Dapps have included supported for contractURI() for years without an ERC to reference. This standard also introduces the event ContractURIUpdated() to signal when to update the metadata.

Specification

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119 and RFC 8174.

The contract MUST implement the below interface:

interface IERC7572 {
  function contractURI() external view returns (string memory);

  event ContractURIUpdated();
}

The string returned from contractURI() MAY be an offchain resource or onchain JSON data string (data:application/json;utf8,{}).

The ContractURIUpdated() event SHOULD be emitted on updates to the contract metadata for offchain indexers to query the contract.

If the underlying contract additionally provides a name() method, the metadata returned by contractURI()’s name property is RECOMMENDED to take precedence. This enables contract creators to update their contract name with an event that notifies of the update.

Schema for contractURI

The schema for the JSON returned from contractURI() MUST conform to:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "The name of the contract."
    },
    "description": {
      "type": "string",
      "description": "The description of the contract."
    },
    "image": {
      "type": "string",
      "format": "uri",
      "description": "A URI pointing to a resource with mime type image/* that represents the contract, typically displayed as a profile picture for the contract."
    },
    "banner_image": {
      "type": "string",
      "format": "uri",
      "description": "A URI pointing to a resource with mime type image/* that represents the contract, displayed as a banner image for the contract."
    },
    "featured_image": {
      "type": "string",
      "format": "uri",
      "description": "A URI pointing to a resource with mime type image/* that represents the featured image for the contract, typically used for a highlight section. The aspect ratio of the image should be 1:1."
    },
    "external_link": {
      "type": "string",
      "format": "uri",
      "description": "The external link of the contract."
    },
    "collaborators": {
      "type": "array",
      "items": {
        "type": "string",
        "description": "An Ethereum address representing an authorized editor of the contract."
      },
      "description": "An array of Ethereum addresses representing collaborators (authorized editors) of the contract."
    }
  },
  "required": ["name"]
}

Example:

{
  "name": "Example Contract",
  "description": "Your description here",
  "image": "ipfs://QmTNgv3jx2HHfBjQX9RnKtxj2xv2xQCtbDXoRi5rJ3a46e",
  "banner_image": "ipfs://QmdChMVnMSq4U7oVKhud7wUSEZGnwuMuTY5rUQx57Ayp6H",
  "featured_image": "ipfs://QmS9m6e1E1NfioMM8dy1WMZNN2FRh2WDjeqJFWextqXCT8",
  "external_link": "https://project-website.com",
  "collaborators": ["0x388C818CA8B9251b393131C08a736A67ccB19297"]
}

Future ERCs MAY inherit this one to add more properties to the schema for standardization.

Rationale

The method name contractURI() was chosen based on its existing implementation in dapps. The event ContractURIUpdated() is specified to help offchain indexers to know when to refetch the metadata.

Backwards Compatibility

As a new ERC, no backwards compatibility issues are present.

Reference Implementation

contract MyCollectible is ERC721, IERCXXXX {
    string _contractURI = "ipfs://QmTNgv3jx2HHfBjQX9RnKtxj2xv2xQDtbVXoRi5rJ3a46e"
    // or e.g. "https://external-link-url.com/my-contract-metadata.json";

    function contractURI() external view returns (string memory) {
        return _contractURI;
        // or e.g. for onchain:
        string memory json = '{"name": "Creatures","description":"..."}';
        return string.concat("data:application/json;utf8,", json);
    }

    /// @dev Suggested setter, not explicitly specified as part of this ERC
    function setContractURI(string memory newURI) external onlyOwner {
        _contractURI = newURI;
        emit ContractURIUpdated();
    }
}

Security Considerations

Addresses specified as collaborators should be expected to receive admin-level functionality for updating contract information on dapps that implement this standard.

Copyright and related rights waived via CC0.

Citation

Please cite this document as:

Devin Finzer (@dfinzer), Alex Atallah (@alexanderatallah), Ryan Ghods (@ryanio), "ERC-7572: Contract-level metadata via `contractURI()` [DRAFT]," Ethereum Improvement Proposals, no. 7572, December 2023. [Online serial]. Available: https://eips.ethereum.org/EIPS/eip-7572.