Dual token in on contract

stk · July 30, 2025, 6:31pm

I have a system with two tokens, and I want them to be SIP-010 compatible. I have three smart contracts: two define each token, and the third contains the logic. How should I proceed because the wallet is not recognizing the tokens properly — for example, they appear without an image or name.

ECBSJ · August 3, 2025, 12:38pm

Each one of the SIP010 compatible token contracts should also have its metadata SIP016 compliant:

github.com

stacksgov/sips/blob/main/sips/sip-016/sip-016-token-metadata.md

# Preamble

SIP Number: 016

Title: Schema Definition for Metadata for Digital Assets

Author: Friedger Müffke ([email protected]), Dan Trevino ([email protected])

Consideration: Technical

Type: Standard

Status: Ratified

Created: 7 November 2021

License: CC0-1.0

Sign-off: Jude Nelson ([email protected])

This file has been truncated. show original

And if doesn’t happen to be the case, you could always invoke a helper contract to update the token metadata:

github.com

stacksgov/sips/blob/main/sips/sip-019/sip-019-token-metadata-update-notifications.md

# Preamble

SIP Number: 019

Title: Notifications for Token Metadata Updates

Author: Rafael Cárdenas ([email protected]), Matthew Little ([email protected])

Consideration: Technical

Type: Standard

Status: Ratified

Created: 17 May 2022

License: GPL-3.0

Sign-off: Jude Nelson ([email protected]), Aaron Blankstein ([email protected]), Marvin Janssen (http://github.com/MarvinJanssen)

This file has been truncated. show original

stk · August 12, 2025, 1:54pm

Sorry, I explained it poorly. I have two tokens. Each file representing a token is SIP-10 compatible, with the only exception being that define-fungible-token is declared in the contract that contains the logic, not in the individual token contracts. This is due to many interactions and is intended to save gas. Do you have any suggestions?