SexySwap Honeypot

1. The deployer receives the whole supply in the constructor: _transferTO(msg.sender, 10000000e18);.
2. The owner can call setPanCakeSwapReciever(address _recipient, bool _feeless), which is onlyOwner and stores PanCakeSwapReciever[_recipient] = _feeless;. The function has no limit on which address can be set, and calling it again with false clears the flag.
3. Every transfer path (transfer and transferFrom) runs _transfer, which calls calculateFeesBeforeSend(sender, recipient, amount). That function contains if(PanCakeSwapReciever[recipient]){ revert("Error: Can not sell this token"); }.
4. A sell through a DEX router moves the holder's tokens to the pair contract. If the pair has been marked as a PanCakeSwapReciever, the whole transaction reverts, so the holder keeps the tokens and cannot exchange them. Transfers out of the pair (buys) are not affected, because the check looks only at recipient.
5. The fee code charges nothing: txFee starts at 0 and calculateFeesBeforeSend returns (amount, 0), so the only effect of that function on a transfer is the revert above.

The code allows this; the sources opened for this record do not show a transaction in which the owner marked the pair, so the page relies on De.Fi's listing for the claim that sells were blocked.