[x] Need to confirm about policyId and mintPolicy, unclear how these should be filled
policyId is supposed to have a MintingPolicyHash for the collection nft currency symbol, not sure how to get that since we only have the currency symbol
Nevermind, a currency symbol is a policy hash and serialization-lib can be used to convert the bytes to ScriptHash
mintPolicy is just an arbitrary version string, maybe it's okay to have it empty for now
[x] Need to confirm which ownerPkh (and ownerPrice) go in the metadata: the value for the input token or the output token
Given that the minting transaction would need to include the output token's information, and the updated owner would be required for the output token to be used at all, the value for the output token seems like the correct choice
[x] Need to use changes from #7 and import metadata code from updated location
[x] Use updated public api currencysymbol in metadata code (need to update CTL to a point which includes these changes)
I'm currently converting from Contract.Value.CurrencySymbol to Cardano.Types.Value.CurrencySymbol because of a discrepancy between the metadata and the NftCollection types, maybe the metadata code can be converted to use the Contract.Value.CurrencySymbol (since I believe that is the "public api" and best practice)
[x] I'll probably also extract the metadata-adding to its own function
[x] The build is currently broken because of a bug in the build system
Addresses #8
policyId
andmintPolicy
, unclear how these should be filledpolicyId
is supposed to have aMintingPolicyHash
for the collection nft currency symbol, not sure how to get that since we only have the currency symbolScriptHash
mintPolicy
is just an arbitrary version string, maybe it's okay to have it empty for nowownerPkh
(andownerPrice
) go in the metadata: the value for the input token or the output tokenContract.Value.CurrencySymbol
toCardano.Types.Value.CurrencySymbol
because of a discrepancy between the metadata and theNftCollection
types, maybe the metadata code can be converted to use theContract.Value.CurrencySymbol
(since I believe that is the "public api" and best practice)