Add necessary function for supporting mint functionality for nft1 parent tokens. In Cashtab, this would be used by an NFT creator to increase the supply of an NFT collection.
Not yet implemented.
Details
Details
- Reviewers
emack - Group Reviewers
Restricted Project - Commits
- rABCd502a7dfe0e2: [Cashtab] Add function to generate target outputs for an slpv1 nft parent mint…
npm test
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- next-nft-fn
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 28574 Build 56689: Build Diff cashtab-tests Build 56688: arc lint + arc unit
Event Timeline
Comment Actions
On a related note, are we sticking with the whole parent vs child terminology all the way through to the frontend? I recall back in 2021 there was discussion on using more user friendly terminology in the frontend, like using "Collection" for parent and "NFT" for child. This way it'll be a smoother experience for users who are used to NFT terminology from other chains.
Comment Actions
On a related note, are we sticking with the whole parent vs child terminology all the way through to the frontend?
no, we'll use something better. Probably "Collection" and "NFT"
parent and child are useful terms for the dev functions since they correspond with similar terms in the spec and the lib (and because there are weird technicalities, like the parent token is technically an nft, but not the same kind as a child nft, etc). But front end should be less complicated.