How to mint with a custom token ID in an ERC721 collection?

[niwaa]

Hi, I've created an ERC721 contract collection using the Rarible.com UI. I would like to programmatically mint NFTs with custom token Ids, something that the Rarible.com UI interface doesn't allow.

I have been playing with the ethereum example and the sdk.nft.mint can accept an nftTokenId but this require a signature. If I use the generate_token_id API calls, this gives me random token_ids with the signature.

Is that even possible to pass specific tokenId?

Can I use something like https://docs.rarible.org/ethereum/assets/creating-an-asset/#erc721-standard-minting
to pass any tokenId I would like?

[evgenynacu]

Hey.
It's possible to skip generate token id endpoint if you know how to work with IDs. But it's probably possible only when you have separate contract.

Also, you should take in account that in the new contracts you should use special token IDs: they should begin with user address.

Could you tell me more about the case you are thinking about?

[niwaa]

The use case was just to have token Ids matching the item collection number.
Yes I have a separate contract... I think I found a way to generate signature for a custom token id, using private key. It seems to work on rinkeby testnet, so it should work on the mainnet too.

[Theo6890]

Hey. It's possible to skip generate token id endpoint if you know how to work with IDs. But it's probably possible only when you have separate contract.

Also, you should take in account that in the new contracts you should use special token IDs: they should begin with user address.

Could you tell me more about the case you are thinking about?

by But it's probably possible only when you have separate contract. do you mean a tailored contract?

and an id must be: owner address (0x42eb768f2244c8811c63729a21a3569731535f06) + tokenId (52), so that gives 0x42eb768f2244c8811c63729a21a3569731535f0652, right?