Skip to main content
9 events
when toggle format what by license comment
Jul 6, 2022 at 6:03 comment added sean Yea that’s right. Depending on your use case one idea to solve for randomness could be to sell a „random“ lottery ticket token first and have that secretly tied to an NFT that the user can claim in a second transaction 🤔
Jul 6, 2022 at 1:50 comment added Alicia Basilio But is imposible to add random characters image with this right? since user can see tha transaction that they are signing... unless using some source of randomless... wich i currently do not know any...
Jun 10, 2022 at 5:55 comment added sean The question is about an "nft collection" owned by the op, and such a collection usually shares the same minting policy, so you can verify authenticity (check which nft really belongs to this original collection). This policy would usually restrict who can mint nfts that belong to this collection and hence you'd likely have a central authority providing this signature (the key for this should be kept safely on the backend). Technically though you're right in that you can mint nfts also in the wild without any such measure.
Jun 9, 2022 at 23:02 comment added LKBH Pools I am not sure, why you need the NFT creation to be signed by your backend. The NFT belongs to the person who is minting and hence being signed by him should be enough or not ? Or else we are centralising the whole thing and adds extra unnecessary work. Pls correct me ... with arguments.
Jun 5, 2022 at 9:08 vote accept renzCNFT
Jun 5, 2022 at 9:07 comment added sean You mint a token by submitting a „minting transaction“ through the tx submit endpoint. That transaction needs to be created either in the browser or in your backend beforehand.
Jun 5, 2022 at 9:04 comment added renzCNFT It seems that blockfrost doesn't have any apis for minting. cardano.stackexchange.com/questions/3726/…
Jun 5, 2022 at 9:02 history edited sean CC BY-SA 4.0
added 192 characters in body
Jun 5, 2022 at 8:51 history answered sean CC BY-SA 4.0