Skip to content

Conversation

@davidrichards-da
Copy link

This PR adds a logo url field to the token metadata API. This has been a suggestion from multiple wallet providers and would enable token issuers the ability to add an image / logo to an asset providing consistent asset image visualization.

Copy link
Contributor

@meiersi-da meiersi-da left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

to the logo image associated with the token. Asset Issuers can use this field
to supply an image / logo of the token for integration into exchanges, wallets
and user interfaces. It's recommended that the image should be a 200x200 pixels
in size, in PNG, JPEG, or WEBP format with a transparent background.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need to add a metadata key for that, as this info is not shipped on-ledger, but off-ledger where we can just extend the OpenAPI spec here: https://github.com/hyperledger-labs/splice/blob/1200346d5e8efee5dcb282e0ea1061db22725af6/token-standard/splice-api-token-metadata-v1/openapi/token-metadata-v1.yaml#L128-L169

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I've moved the section to the suggested location

in size, in PNG, JPEG, or WEBP format with a transparent background.

##### Metadata Key Syntax

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At the bottom there's a changelog. Please add an entry there.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

Copy link
Contributor

@meiersi-da meiersi-da left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks from the perspective of an author of CIP-56 this looks like a sensible addition to me. I've also created the draft of the API changes we are talking about here:

They are backwards-compatible and easy to put in place.

@waynecollier-da @davidrichards-da : can you coordinate wrt how to get approval and how to ensure all wallet providers and asset issuers learn about this feature once it is supported?


* **2025-03-18:** - Initial Draft
* **2025-03-31:** Approval announced via [mailing list thread](https://lists.sync.global/g/cip-announce/topic/cip_0056_canton_network/112004244)
* **2025-11-25:** - Addition of the Logo URL optional field in the off-ledger token metadata API
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* **2025-11-25:** - Addition of the Logo URL optional field in the off-ledger token metadata API
* **2025-11-25:** - Addition of the Logo URL optional field in the off-ledger token metadata API ([draft PR](https://github.com/hyperledger-labs/splice/pull/3210))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

No open projects
Status: draft

Development

Successfully merging this pull request may close these issues.

2 participants