Skip to content

Latest commit

 

History

History
90 lines (63 loc) · 6.76 KB

pull_request_template.md

File metadata and controls

90 lines (63 loc) · 6.76 KB

New Listing: SYMBOL

  • Identity Name: PROVIDE_NAME_OF_ASSET
  • Authbase: PROVIDE_TXID

Evidence Linking Authbase to Identity

  • Select one:
    • Direct evidence: a chain-resolved registry at the authhead provides substantially equivalent metadata for this authbase. The Authhead TXID is provided below:
    • Indirect evidence: the identity is burned or provably locked within a covenant, so the authbase can safely be linked using indirect evidence. Details and two or more corroborating, third party-archived URLs of reputable sources vouching for this association are provided below:

Evidence Linking Identity to Authbase

Archived URL(s):

Evidence Linking Authbase to Categories

  • Select one:
    • Token category is equal to the authbase for all Identity Snapshots.
    • Evidence is provided for differing category values below:

Substantiation of Other Claims

  • Select one:
    • The submission (esp. the description) includes no claims requiring substantiation.
    • The claims in this submission can be corroborated with the following evidence:

Checklist

  • I have reviewed the OpenTokenRegistry inclusion criteria, and this listing can be included in the registry.
  • The listing completes all required fields:
    • name
      • Objective, authoritative, and neutral tone
      • No longer than 20 characters; exceptions may be allowed for existing legal names (please provide evidence above including the jurisdiction(s) in which the legal name is established).
    • description
      • Objective, authoritative, and neutral tone
      • Descriptions is appropriate for use in user interfaces without a disclaimer by unaffiliated, neutral, third parties (wallets, block explorers, exchanges, etc.); no exclamations, calls to action, or disputable statements.
      • All claims are substantiated above.
    • token information (if applicable)
      • Token category is defined.
      • If fungible tokens exist for the category, decimals is defined.
      • symbol
        • Globally-unique base symbol, including among assets not listed in OpenTokenRegistry.
        • Valid symbol (regular expression: /^[A-Z0-9]+[-A-Z0-9]*$/)
        • Appropriate minimum length (For new, primarily-fungible base symbols: minimum of 4 characters; non-fungible base symbols: minimum of 6 characters; see Symbol Length Recommendations)
        • No longer than 13 characters for base symbols
        • No longer than 26 characters for full symbols
    • uris.icon
      • Uses IPFS with a v1 CID. To convert a v0 CID (begins with Qm...), try dweb.link. For example, QmcNL1KcVmiDtwJe8WokrnzYeoHirsz1sNxNojncsxyb2p is a v0 CID. It can be viewed at https://dweb.link/ipfs/QmcNL1KcVmiDtwJe8WokrnzYeoHirsz1sNxNojncsxyb2p, which redirects to a subdomain equal to the v1 CID: https://bafybeigqogqx3n4cldk6nizl5vihopi2dkgvw4yqamc5rhleyqu25soe4e.ipfs.dweb.link/. The correct URI for this icon is: ipfs://bafybeigqogqx3n4cldk6nizl5vihopi2dkgvw4yqamc5rhleyqu25soe4e.
      • Either SVG format OR 400px by 400px AVIF, WebP, or PNG
    • uris.web
      • Domain name is owned by the issuing project or organization
      • Either HTTPS protocol OR ongoing activity demonstrated via optional URI identifiers (described in Substantiation of Other Claims)
    • Includes relevant historical information in previous snapshots OR this token has never been rebranded, redenominated, or reissued
    • All static data (images, animations, videos, binary files, etc.) uses IPFS with v1 CIDs to ensure file integrity (e.g. ipfs://ba...).