Possible validation bug?

[4LPH4M3M0RY]

When I try to upload a lazy mint NFT to the url: https://ethereum-api-dev.rarible.org/v0.1/nft/mints,
I receive the following error:

{"code":"VALIDATION","message":"TokenId Token(id=0xb0ea149212eb707a1e5fc1d2d3fd318a8d94cf05, owner=0x6751c1ebdc4ab4e5cb103d5ceb84d26963a3377e, name=Rarible, symbol=RARI, status=CONFIRMED, features=[APPROVE_FOR_ALL, MINT_AND_TRANSFER], lastEventId=null, standard=ERC721, version=2, isRaribleContract=true) must start with first creator address","status":400}

Everything seem to be filled in correctly (This is how the json file looks:

{
  "@type": "ERC721",
  "contract": "0xB0EA149212Eb707a1E5FC1D2d3fD318a8d94cf05",
  "tokenId": 125,
  "uri": "ipfs:\/\/ipfs\/QmVSjd9zQfBP4FjsBMvV2sFLMywRsa9zp4NwBRGmzjpaaB",
  "creators": [
    {
      "account":"0xC64BCDEE18f356a1818C43Efa3dA2F723545f0Bz",
      "value":10000
    }
  ],
  "royalties": [
    {
      "account": "0xC64BCDEE18f3536a1818C3Efa3dA2F723545f0Bz",
      "value": 1000
    }
  ],
  "signatures": [
    "0x46ff572a2a0b8defc387dca4ec9e5121d371ea3a95af9fea56e6f37a085b5e43"
  ]
}

[bobwith2bees]

Couple of things to check:

• tokenId in the form should be a string containing a whole integer number (not hex) and quoted, not a json integer (without quotes).
• the tokenID should be much larger than 125... in hex it is your minter address shifted left a bit to make space for the next sequence number (which if you are just starting - would start from 1)
• Review your call to get next token id. Make sure you are on the correct collection contract. You can verify the contract address is correct using your browser. For example chain id 4 (Rinkeby) you can see the collection here: https://rinkeby.rarible.com/collection/0xB0EA149212Eb707a1E5FC1D2d3fD318a8d94cf05 . (and make sure that chainId is in the signing request for the ERC712 domain definition. You'll hit a signature error later otherwise.)
• Verify the collection supports lazy minting and the rarible protocol. You should have created your own collection from a TokenFactory, or ensured you support the proper API (I'll defer to the pros on this point.) You can also use the provided rarible collections posted on the addresses page. https://docs.rarible.org/ethereum/contract-addresses/

[evgenynacu]

You are absolutely right, OP should check how he gets this token id (125). If this id was generated by our API then it's a bug.

But also want to tell that our backend should support all kinds of data: number, string and hex string

[shashank42]

Couple of things to check:
...

• Verify the collection supports lazy minting and the rarible protocol. You should have created your own collection from a TokenFactory, or ensured you support the proper API (I'll defer to the pros on this point.) You can also use the provided rarible collections posted on the addresses page. https://docs.rarible.org/ethereum/contract-addresses/
  Maybe this is what I am missing

Have deployed the contract here which supports lazy minting works with 1 creator but doesn't support it for 2 creators.
https://ropsten.etherscan.io/address/0xD8e6A2f59Edc32814a4ac9271715d54bAF21239E#contracts

But while using the contract (0xB0EA149212Eb707a1E5FC1D2d3fD318a8d94cf05) from https://docs.rarible.org/ethereum/contract-addresses/ lazy minting with any number of creators work. Can you help?

Data used for lazy minting with 2 creators which doesn't work (Internal server error 500) on "https://ethereum-api-dev.rarible.org/v0.1/nft/mints"

{"@type":"ERC721","contract":"0xD8e6A2f59Edc32814a4ac9271715d54bAF21239E","tokenId":"109330708243965094921642637063714744979272596568623722532879042507132165423116","uri":"/ipfs/Qmc7hPdKBfLpsWCpkyVdg4QG2kwqyuXv3Aqb17fr1McBcU","creators":[{"account":"0xf1b6fceac6784a26360056973c41e0017dee12e4","value":9000},{"account":"0xc7b4240e35fef032e68612be497f06d9fd421cf4","value":1000}],"royalties":[{"account":"0xf1b6fceac6784a26360056973c41e0017dee12e4","value":1000},{"account":"0xc7b4240e35fef032e68612be497f06d9fd421cf4","value":500}],"signatures":["0x53592edfee98dde8695af8653fc421f33cd6ee9538d18ea6a27f4c65622d7b8f50d5ed43a6e58187b1f52788b40457fcf3b2b74b5e9145084e071fbdf7ab57981b","0x370d9efc2e64970e026628b5e8f1c294f18d8e6066cde5101293fdfe40a36a6204d8bcaebfcb57c2c525350f77e74f22ecfa5e4a5a0c355881623ed666a092ad1b"]}

This is the request that works on my deployed contract on Ropsten with 1 creator

{ '@type': 'ERC721',
     contract: '0xD8e6A2f59Edc32814a4ac9271715d54bAF21239E',
     tokenId:
      '109330708243965094921642637063714744979272596568623722532879042507132165423121',
     uri: '/ipfs/Qmc7hPdKBfLpsWCpkyVdg4QG2kwqyuXv3Aqb17fr1McBcU',
     creators: [ [Object] ],
     royalties: [ [Object], [Object] ],
     signatures:
      [ '0x0755ad556043637afd7b8553d693128b971855b2621b08cfa4f38b0fd2e824a02e4a3b866ba04c529f4f5b068fa597ff0bf32461d0757cab0e8dfa3f807327be1b' ] }

And here is the request that works on the Rarible deployed contract on Ropsten

{ '@type': 'ERC721',
     contract: '0xB0EA149212Eb707a1E5FC1D2d3fD318a8d94cf05',
     tokenId:
      '109330708243965094921642637063714744979272596568623722532879042507132165423237',
     uri: '/ipfs/Qmc7hPdKBfLpsWCpkyVdg4QG2kwqyuXv3Aqb17fr1McBcU',
     creators: [{"account":"0xf1b6fceac6784a26360056973c41e0017dee12e4","value":9000},{"account":"0xc7b4240e35fef032e68612be497f06d9fd421cf4","value":1000}],
     royalties: [ [{"account":"0xf1b6fceac6784a26360056973c41e0017dee12e4","value":1000},{"account":"0xc7b4240e35fef032e68612be497f06d9fd421cf4","value":500}] ],
     signatures:
      [ '0x9b507fcdda4af21f8fdeb6205db4ec409fc42783d0502d8518b1f91e7a226662006127ed2b44a248022a279196fa9b06442f01717d2372355065cad39a384df91c', '0xacc7edc541990df9cb90c45d7224bd6d255931d871d115c177344061b54447e355c663e696e7cc3b567962786d592269e332d534f84295ab9908d06b7562bb6a1c' ] }