using the CreatorContract in a Next JS / Typescript project

[Booker-CU]

Hello... I am having trouble implementing the creatorClient contract in NextJS w/ Typescript..

Here are my 2 function.
I am passing in an imagebuffer which is an AI generated image.
How do I use it inside the creatorClient.create1155 function?

Do I first need to do something w/ makeImageTokenMetadata, makeContractMetadata first to get the token and contract uri's? -- but then what do I do?

Also how would I call them correctly (makeImageTokenMetadata, makeContractMetadata)

thanks

import {
    useAccount,
    useWriteContract,
} from "wagmi";

import { creatorClient, publicClient } from "../config/zoraConfig";
import { makeImageTokenMetadata, makeContractMetadata } from "./zoraMetaDataUtil";

export async function createNFT(imageBuffer: string) {

    const { address } = useAccount();

    if (!publicClient || !address) {
        throw new Error("No public client or address found");
    }

    const { parameters, contractAddress} = await creatorClient.create1155({

        contract: {

            //Contract Name
            name: "My NFT Collection",

            //Contract Metadata URI
            uri: "ipfs://DUMMY/contract.json",
        },
        token: {
            tokenMetadataURI: "ipfs://TOKEN_URI",
        },
        account: address,
    });

    return { parameters, contractAddress };
}

export async function executeMint(parameters: any) {
    const { writeContract } = useWriteContract();
    const { abi } = parameters

    try {
      const txResult =  await writeContract(
        parameters.contractAddress,
        abi,
    );
      console.log(txResult)
      return txResult;
    } catch (error) {
      console.error('Error during NFT mint:', error);
      throw error;
    }
}

[iainnash]

We strongly recommend using an IPFS service to upload your image before posting and incorporate that url in the make contract and token metadata fields. There are a number of IPFS services that will handle standard NFT metadata and docs on the spec here: https://docs.zora.co/contracts/Metadata

Let us know if we can help clarify this information further :).

[Booker-CU]

We strongly recommend using an IPFS service to upload your image before posting and incorporate that url in the make contract and token metadata fields. There are a number of IPFS services that will handle standard NFT metadata and docs on the spec here: https://docs.zora.co/contracts/Metadata

Let us know if we can help clarify this information further :).

thanks for the message... was curious, does the writeContract function return anything?

const txResult = await writeContract(
parameters.contractAddress,
abi,
);
it says its returning type VOID

Thanks

[Booker-CU]

have another question... I am now using 'ipfs-http-client' to pin image to ipfs...

//Pin ImageBuffer to IPFS
const { cid } = await ipfs.add(imageBuffer);
console.log('Image pinned to IPFS with CID:', cid.toString());
what do I do with makeImageTokenMetadata & makeContractMetadata functions (zoralabs sdk)... do I need to pass them both the cid, since the image is pinned to ipfs do I need to change part of the makeImageTokenMetadata function?

thanks

[iainnash]

You need to pass in the cid using `ipfs://${cid}` for the urls. You can use the same url if you want the same metadata for the contract and token or different metadata.

…

On Fri, Oct 25, 2024 at 16:51 Booker ***@***.***> wrote: have another question... I am now using 'ipfs-http-client' to pin image to ipfs... //Pin ImageBuffer to IPFS const { cid } = await ipfs.add(imageBuffer); console.log('Image pinned to IPFS with CID:', cid.toString()); what do I do with makeImageTokenMetadata & makeContractMetadata functions (zoralabs sdk)... do I need to pass them both the cid, since the image is pinned to ipfs do I need to change part of the makeImageTokenMetadata function? thanks — Reply to this email directly, view it on GitHub <#462 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGMCOABFXDI7DGXG5QDHBTZ5KVO5AVCNFSM6AAAAABQSKO6KOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZYG44DENJVGY> . You are receiving this because you commented.Message ID: ***@***.***>