ERC1155 Metadata: OpenSea not replacing {id} with actual token ID?

Smart Contracts
1

I'm wondering if there are cases when OpenSea (or any client) does not replace {id} in Metadata JSON files.

If the string {id} exists in any JSON value, it MUST be replaced with the actual token ID, by all client software that follows this standard.

I have a case where OpenSea is simply rendering {id} as plain text for the following file:

{
  "name": "Token id {id}",
  "description": "This is #{id} ",
  "image": "https:\/\/url.com/img?id={id}"
}
1 Like