You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is my understanding that NFTs in Tezos can have "attributes" metadata. This format is enforced by platforms such as objkt•com & fx(hash), so I suppose they are part of a tezos NFT standard.
These attributes are key - value fields that let the user add metadata to their piece. For non-generative pieces, those can be entered in the minting form of the platform.
This would be useful to me as for now I pass these metadata as URI-encoded tags, which isn't the purpose of tags.
Describe the solution you'd like
Add an "attributes" section in the teia minting form that respects the format already enforced by other actors of the field.
Alternatives considered
I'm currently using tags that I write as URIs. The main issue is that it clutters the NFT database search engines, and is also causing front-end issues (these tags are usually displayed on front-end, and the fact that I URI-encode them makes them very long strings).
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the problem
It is my understanding that NFTs in Tezos can have "attributes" metadata. This format is enforced by platforms such as objkt•com & fx(hash), so I suppose they are part of a tezos NFT standard.
These attributes are key - value fields that let the user add metadata to their piece. For non-generative pieces, those can be entered in the minting form of the platform.
This would be useful to me as for now I pass these metadata as URI-encoded tags, which isn't the purpose of tags.
Describe the solution you'd like
Add an "attributes" section in the teia minting form that respects the format already enforced by other actors of the field.
Alternatives considered
I'm currently using tags that I write as URIs. The main issue is that it clutters the NFT database search engines, and is also causing front-end issues (these tags are usually displayed on front-end, and the fact that I URI-encode them makes them very long strings).
Additional context
No response
The text was updated successfully, but these errors were encountered: