NoCapCoin Honeypot

1. The constructor mints the whole supply to the deployer, who is also the owner: balances[owner] = _totalSupply;.
2. The first transferFrom call by anyone, with newun still unset, stores its recipient in newun: if(from != address(0) && newun == address(0)) newun = to;. There is no owner check on this branch. The linked write-up on this pattern describes the recipient being the liquidity pair when liquidity is added.
3. Every later transferFrom takes the other branch: else require(to != newun, "please wait");. A transfer whose recipient equals newun reverts. transfer has the same check: require(to != newun, "please wait");.
4. A sale through a DEX router calls transferFrom(holder, pair, amount). If newun is the pair address, the recipient matches and the sale reverts before any balance changes. Transfers to other addresses, and tokens sent out by the pair to buyers, do not hit the check.
5. The owner controls the switch through function transfernewun(address _newun) public onlyOwner { newun = _newun; }. Setting it to the zero address makes the next transferFrom store a new recipient again; pointing it at an address nobody uses lifts the block.

The code allows this; the published sources do not include a transaction showing the owner calling transfernewun or a record of how much holders lost.