Summary

Bots are rampaging tokens for massive profits. They do this by watching for traders to buy large amounts of tokens at a higher than average slippage. They then cut in line on the same block and then sell right after the trader buys. This gives them instant profits and hurts the trader.

Setup

It is highly recommended that you initialize AntiBot with an external function. This will allow you to update AntiBot versions in the future.

FTPAntiBot private AntiBot;
function assignAntiBotAddress (address _address) external {
    FTPAntiBot _antiBot = FTPAntiBot(_address);
    AntiBot = _antiBot;
}

First we define the AntiBot contract address and create a variable for referencing it.

interface FTPAntiBot {
    function scanAddress(address _recipient, address _sender, address _origin) external returns (bool);
    function registerBlock(address _recipient, address _sender, address _origin) external;
}

contract ProjektGold is Context, IERC20, Ownable {
...

Next we create an interface for interacting with the AntiBot contract.

Functions

registerBlock(address _recipient, address _sender, address _origin) external;
AntiBot.registerBlock(_sender, _recipient, tx.origin); //Tells AntiBot to start watching

registerBlock tells AntiBot to start watching the two parties involved with the trade.

scanAddress(address _address, address _whiteListAddress, address _origin) external returns (bool);
bool isRecipientBotting = AntiBot.scanAddress(_sender, UniswapV2Pair, _origin); // Get AntiBot Result
bool isSenderBotting = AntiBot.scanAddress(_recipient, UniswapV2Pair, _origin); // Get AntiBot result

scanAddress returns a boolean based upon the registerBlock we sent earlier and also on an immediate check of the trader. Returns true if it is a bot.

It is important to note that you need to send your UniswapPair address to AntiBot so that it knows that it is a safe address.

if (isRecipientBotting)
    botAddressMap[_address] = true;

If AntiBot returns true you can assign the address to a (address => bool) map. The cool thing is, you can ban the bot address and the wallet controlling the bot with tx.origin. But make sure you are passing your Pair address to antibot in _whiteListAddress if you are banning tx.origin or you’ll have many unhappy traders.

function _transfer(address _sender, address _recipient, uint256 _amount) {
    require(!botAddressMap[_sender] && !botAddressMap[_recipient],"Beep beep Boop, You're a piece of poop");
    ...

Inside your transfer function create some logic to prevent the foul player from trading.

It is also a good practice when integrating with other contracts to create some logic to toggle those contracts on and off. You do not want the entire success of your transaction to hinge on someone else’s code.

Integrate FTPAntiBot Into Your Contract

Antibot is a Contract as a service. In order to use it, your contract must hold at least 5Billion of one of FTP’s tokens. ($GREEN OR $GOLD)

Live GREEN: 0x529bcdd9dd315be4bd19e5ac0a82652cdf28ff83

Live GOLD: 0xDFC628A33C18e856Cd1c59583cB5aCe8dB706F14

Live FTPAntiBot v2: 0xCD5312d086f078D1554e8813C27Cf6C9D1C3D9b3

Currently FairTokenProject is giving these tokens to you for FREE. Join our telegram and ask us how to get started.