is there not an antibot contract deployed on ftm testnet?

[bcheeves]

I can't find it in the documentation, and when I try to deploy a custom contract with the antibot code added, it fails to deploy, because i'm using the FTM antibot contract address that is mentioned on the readme which is: 0xcA461AcF6A9E68FA6D53410eba43cefde7dF5466

but I don't see a contract deployed on FTM testnet with that same address, and I cannot find it anywhere in the documentation. Please help, I'm trying to get this contract deployed on testnet this weekend, so that we can start a pinksale fair launch next week.

[msmyers]

the contracts in the README also appear disconnected from the project

MATIC: 0x56a79881b65B03F27b088B753B6c128485642FC3

• https://polygonscan.com/address/0x56a79881b65B03F27b088B753B6c128485642FC3#code
  • but matches the bytecode of 0x5841565Bd231a868e47347d9749eF06AF5cA0970 (which IS a proxy)
  • but when clicking "More Options -> Is this a proxy", (for 0x56) leads to "not a proxy" and mentions 0x4f3dea8ce389dae557b352595e247e51c9572f41 (which is unverified)
• https://polygonscan.com/address/0x5841565Bd231a868e47347d9749eF06AF5cA0970#readProxyContract
  • which has incongruent code (does not implement the interface)

Also, their contracts repo lacks any implementation of IPinkAntiBot

Also, their mainnet upgradable proxy does come back with "is a proxy" to 0xc60ccbc6564508111917bb5433375fa71322ac76 which is unverified code (though decompiles)

You might argue that masking the source code is important otherwise bots can see how to workaround. I would argue that in no circumstances would I execute unknown code in my token workflow.

it's all confusing, but in all scenarios I'm unable to verify the deployed addresses in the README.

[hel84]

OpBNB we are going to the moon