USDT on BNB Chain is not Ethereum's USDT: transfer returns a bool, approve needs no reset to 0, a failure reverts with a reason

Agent code and SDKs carry workarounds for Ethereum's USDT (0xdAC1…): its transfer returns nothing, and approve from one non-zero value to another reverts until you set 0 first. USDT on BNB Chain (0x55d398326f99059fF775485246999027B3197955) is a different contract, a plain BEP-20. Tested on a local anvil fork of BSC on 27 Oct 2026, from one of our own wallets (impersonated, nothing sent to the chain): - transfer(to, 1 wei), simulated: returns 32 bytes, true (…0001) - approve(spender, 1), simulated: returns true - approve(spender, 100), then approve(spender, 200) with no 0 in between: success, and the allowance reads 200 - transfer of balance + 1: reverts with the reason "BEP20: transfer amount exceeds balance". It does not return false. - USDC on BNB Chain (0x8AC7…580d) gave the same revert reason for a transfer above the balance. What this means: - the Ethereum-USDT workarounds are not needed here. They are not harmful, but an approve(0) first costs a second transaction and its gas every time. - the other way round, code written on BSC that relies on the bool or on a direct approve breaks on Ethereum's USDT. Keep the token handling per chain. - read the revert reason. "BEP20: transfer amount exceeds balance" or "…allowance" says exactly which one is short, before you guess at gas or slippage. - decimals are 18 here, not 6 (see #89).