Invalid token ID in transaction history of BAYC

Hi there!

I’ve downloaded all transaction history for research purposes. However, from the 26700 rows of transaction data, we have found 12 invalid BAYC token ID. From the beginning, only 10000BAYC tokens were minted, with its token ID ranging from 0-9999. However, we have found abnormally long token Ids such as β€œ554646570449631968…” and so on. Does anyone have any read on this situation?!

Can you paste those invalid token ids that you found?

Also the transaction id if possible

[β€˜28046’, β€˜28047’, β€˜23924’, β€˜22965’, β€˜21124’, β€˜55464657044963196816950587289035428064568320970692304673817341489687899934720’, β€˜23843’, β€˜18800’, β€˜18801’, β€˜20466’, β€˜20467’, β€˜13468’, β€˜13469’, β€˜27870’, β€˜25970’, β€˜25971’, β€˜10156’, β€˜26524’, β€˜26525’, β€˜23446’, β€˜23447’]

is the list of the invalid token IDs

[β€˜0x0785b1d8def6f0fc6d4d27472233462f07f5ff93ddd4f58c2b82b955c68e308d’,
β€˜0xfda9c6e092c791673e62e194d545d5c2edcb65c2a36e4a3c828eeafd6f15bf17’,
β€˜0x9f9c632c73dc5c8a34332151c965e4e83bdac6c552f3048c5c93e66c190ab685’,
β€˜0x88fe6c8207a93159a1f0436ccf9117a45a495b533d0c80508dc2593652cd5c94’,
β€˜0x1b99ffb73a3423ebbdbd7bc3108f7315ffcd48892d79a1e2289c05fe34bc048c’,
β€˜0xcaf3dec348d0ef4fe978f840941df4f48cd9700ce26b2a351c0b647f761f5ec7’,
β€˜0x77302e05b0ab828c1a646d774c75f4e812502136637e816ef53900e8e477234e’,
β€˜0x25a4e7465ddd2e9bb1af87688951af0c653ef7a1fbbe65392d78f90280104482’,
β€˜0xf9fc9abce6fcbe8b894cb5766b4b6b7976d433e07b848e673ebc027b15033204’,
β€˜0x7df75599f01fdee111eae44f53e545ee8ed97f586dad2f94a787282cae68a6d6’,
β€˜0x1b3a9d43f29d8a86a5fb74643c8c113fcedf3ac5505cc98e670847ecfe117e6f’,
β€˜0x9d832920c1662f9b62b31755cbd683b9ded3b5082c877e5fffb35a150173f39c’]

is the transaction hashes of those weird ones. Thanks!

for the first transaction, it looks like the strange token ids are from this contract 0x60E4d786628Fea6478F785A6d7e704777c86a7c6

Oh interesting, it seems like it’s actualy Mutant Apes Yacht Club which I wasn’t aware of before. Thanks for pointing that out, although still not sure what happend with that token id 55464657044963196816950587289035428064568320970692304673817341489687899934720.

Cheers,