we only link to the action page for this NFT if the user has this NFT in their wallet

(we render all NFTs in a collection)

after sending an NFT

add isNftParent -- this changes when we navigate from a child NFT to its parent. In this case, we also want to load and render the child NFTs of this collection.

mistake that we did not have a param for address here before, as this function is for sending, not minting / genesis

This function only handles the genesis tx of a given token id. We are using txType === 'GENESIS' here to make sure we are looking at the right tokenEntry -- i.e. the one that covers the minting of this NFT -- as that is the tokenEntry that will have groupTokenId.

The other tokenEntry will be about burning the NFT Mint input.

A summary of how we are changing this function. If we see a tokenId for the first time, and we see that it is an SLP1 NFT child -- make sure to get its groupTokenId and save that in cache.

in this segment it reads where if the tx type for this NFT child is a normal send (i.e. txType !== 'GENESIS', the groupTokenId is not updated in cache?

Because this function is only getting a GENESIS tx, we don't expect to see this. Potentially we could be dealing with an ALP tx that is both a genesis and a send tx. In this case, filtering for the tokenEntry with GENESIS should give us the same impact (tho we will never have an ALP tx with SLP_TOKEN_TYPE_NFT1_CHILD so kind of moot).

yes, tho this is implemented at the sendXec callsite, so not relevant to functions that create target outputs.