Metadata standards

Best practices for ecosystem support and compatability

Tokens created on Doppler should attempt to adhere to ecosystem best practices to ensure compatibility across as many supported interfaces as possible. We aim to make it as simple, and flexible, as possible, in order to support a wide range of applications and use cases.

Requirements to be supported within the Doppler Indexer

1. Tokens must be created with a URI stored on IPFS that contains an image field

2. The image field in the URI must also contain another pointer to a valid IPFS CID

Have suggestions? File an issue on the documentation, or get in touch with the team!

Examples

Example token created on Pure Markets

{
  "name": "8453",
  "symbol": "8453",
  "image": "ipfs://QmZEFVUKoQDxsUbsRTgrpdwhwxDM95HbMzc7kjUxjynLDk",
  "x": "",
  "telegram": "",
  "farcaster": "",
  "discord": ""
}

• tokenURI: ipfs://QmTM59ZqHcJgv1EQVWs6e96Hchd3diHW9F9evLWmX2PQCU

• Image: ipfs://QmZEFVUKoQDxsUbsRTgrpdwhwxDM95HbMzc7kjUxjynLDk

• 🔗 https://ipfs.io/ipfs/QmTM59ZqHcJgv1EQVWs6e96Hchd3diHW9F9evLWmX2PQCU

Field	Example
name	8453
symbol	8453
image	ipfs://QmZEFVUKoQDxsUbsRTgrpdwhwxDM95HbMzc7kjUxjynLDk
x
telegram
farcaster
discord

Note: fields can be left empty. Pure.st will not attempt to load social links or icons for empty inputs.

Example token created on Zora

{
  "name": "balajis",
  "ticker": "balajis",
  "image": "ipfs://bafybeibeeqdppfm2iizeaqiobdvn533xyuunjpdspdirju7xf4ykwyindq",
  "content": {
    "uri": "ipfs://bafybeibeeqdppfm2iizeaqiobdvn533xyuunjpdspdirju7xf4ykwyindq"
  }

• tokenURI: ipfs://bafybeiexri3tfd6fgjfume3tovyx6xdppgcapmvbjrqtraxec66pbtrus4

• Image: ipfs://bafybeibeeqdppfm2iizeaqiobdvn533xyuunjpdspdirju7xf4ykwyindq

• 🔗 https://ipfs.io/ipfs/QmTM59ZqHcJgv1EQVWs6e96Hchd3diHW9F9evLWmX2PQCU

Field	Example
name	balajis
ticker	balajis
image	ipfs://bafybeibeeqdppfm2iizeaqiobdvn533xyuunjpdspdirju7xf4ykwyindq
content	ipfs://bafybeibeeqdppfm2iizeaqiobdvn533xyuunjpdspdirju7xf4ykwyindq