Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(NFT Images): Support array image types for CIP-68 #922

Merged
merged 1 commit into from
Feb 16, 2024

Conversation

thaddeusdiamond
Copy link
Contributor

Per the recommendation of the pool.pm team and in compliance with metadata standards, we sometimes see NFT IPFS links represented as arrays of strings. These arrays are meant to be concatenated directly to produce the IPFS link (or data scheme, etc.).

Because the image is retrieved in the send assets page, without this change users are UNABLE to send assets in CIP-68 format (since the decimals do not get properly set in nami/src/api/extension/index.js#1762).

[ Testing: npm test, manually built and submitted tx from Nami ]
[ Test Artifacts: txn 5e342b856efa596da433e3eec4256809cfe9bd9c4c9c39eb316328080ced13f1 ]

Per the recommendation of the pool.pm team and in compliance with
metadata standards, we sometimes see NFT IPFS links represented as
arrays of strings.  These arrays are meant to be concatenated directly
to produce the IPFS link (or data scheme, etc.).

Because the image is retrieved in the send assets page, without
this change users are UNABLE to send assets in CIP-68 format (since the
decimals do not get properly set in `nami/src/api/extension/index.js#1762`).

[ Testing: npm test, manually built and submitted tx from Nami ]
[ Test Artifacts: txn 5e342b856efa596da433e3eec4256809cfe9bd9c4c9c39eb316328080ced13f1 ]
@thaddeusdiamond
Copy link
Contributor Author

@rhyslbw @VanessaPC @DominikGuzei @bslabiak would love any attention you might be able to give to this as it is impacting current minters of NFTs on CIP-68. There is a large collection just minted (Galacticats) where assets are frozen in individuals' wallets.

@rhyslbw
Copy link
Member

rhyslbw commented Feb 13, 2024

Thank you for the fix. We'll test and include in release we're currently preparing

@rhyslbw rhyslbw merged commit d5db5fb into input-output-hk:main Feb 16, 2024
1 check passed
@SmaugPool
Copy link

Note: @thaddeusdiamond, I ("pool.pm team") never gave recommendations about CIP68 and string arrays (string arrays in CIP25 are in the spec so it's a different matter), please don't pseudo quote without sources. Thank you.

@thaddeusdiamond
Copy link
Contributor Author

Fair, I guess I should have worded it as "Per the current behavior of JPG and Pool.PM software" but it must have slipped my mind. Just wanted to show that this Nami behavior is breaking NFTs for folks that are using other ecosystem dApps. Poor wording, my bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants