1. Tickle Beach is not on-chain as it claimed. First, lets check contract, etherscan.io/address/0x6f43…

2. TokenURL is where OpenSea gets image data from. On the code it called another contract CustomRender to get the URL. CustomRender contract address is 0x0e9c0165a60E63870134FD8f611eB432dec1280c etherscan.io/address/0x0e9c…

3. Here is the code of tokenURI from CustomRender contract, it called baseUri to get image and model data, baseUri is set to cdn.ticklebeach.com

4. For example, if token ID is 1, it reads image from cdn.ticklebeach.com/preview/1.png, read model from cdn.ticklebeach.com/animation/1.ht…. All image and model data are hosting on ticklebeach.com. This is no difference than hosting on IPFS.

5. Other on-chain project such as OnChainMonkey® stored all image data on chain, not hosted on any website. OnChainMonkey image data can not be changed. But for Tickle Beach dev, if they change the baseURL of CustomRender, etherscan.io/address/0x0e9c…, all image data will be changed

6. Why you can not see the links of hosting directly from the contract? As explained, their contract called the other contract for tokenURL, and the other contract encoded the jason file. But image data is not on chain.

7. Lets compare to other real on chain project such as OnChainMonkey®, they have full image data on chain inside contract etherscan.io/address/0x960b… While Tickle Beach has no any on chain data inside contract.

8. I would like any dev - to show me where is the code for on chain image data if any

To ben.eth and doʎsd : My law firm, Loevy & Loevy, will be filing a class action against you in your IRL name if you do not refund all of the $PSYOP presale purchasers immediately. Our settlement demand letter has served as an NFT to your ben.eth address, viewable here: