-
Notifications
You must be signed in to change notification settings - Fork 167
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
Enable users to specify which cid version (Qm vs bafy) for uploads #387
Comments
I've put together this observable that attempts to clarify what is currently possible and what is not.
Here is the screenshot Here is the summary
If 49 chars will satisfy contract character limit constraint, than solution is simply to take cid from nft.storage and encode it as base58btc string. Otherwise things are bit more complicated, if files aren't small (<1mb) CIDs can be encoded as v0 base58btc ( |
@jnthnvctr do we have any idea on:
Thanks |
cc @alanshaw |
@crzypatchwork could you please provide some feedback here |
The HEN team mentioned that for minting metadata they need to use a separate IPFS node to generate Qm hashes for their metadata.json because of constraints in the number of characters on the contract side.
It'd be useful potentially to enable users to specify on upload whether they'd like to generate Qm or bafy hashes.
The text was updated successfully, but these errors were encountered: