Windswap Honeypot

What the code allows:

1. The deployer receives the whole supply in the constructor: _mint(msg.sender, 1000000000000000e18);.
2. The gate is on from deployment: bool private TIME = true;.
3. Every transfer runs this check: if(sender != owner() && recipient != owner() && sender != pancake && TIME == true){ revert("FOR VALUE PROTECTION, YOU CAN ONLY SELL 1 Sale PER 30 MIN"); }. A holder who is not the owner, sending to anyone other than the owner, reverts unless the holder's address equals pancake.
4. pancake is not fixed. if(sender == owner()){ pancake = recipient; } overwrites it with the recipient of every transfer the owner sends, and addPancake(address input) lets the owner set it directly. Only the one stored address (plus the owner) can send tokens while TIME is true.
5. The owner alone controls the gate: function setTIME (bool _bool) public onlyOwner { TIME = _bool; }. transData records a timestamp for sells but nothing reads it, so the 30-minute wording has no effect on the revert.
6. Two further owner switches can block individual senders or large sales: GTYA(address _addr, bool _bool) marks a bot sender whose transfers hit require(amount <=0, "bots......"), and fire(uint256 TKP) sets the MAX cap applied to transfers into addresses flagged by POOL.

De.Fi's REKT database lists the token as an exit scam/honeypot where the owner could disable transfers. No transaction showing the owner calling these functions was opened.