# Additional token behavior

The shared Tether token implementation has additional characteristics to account for in your integration. They apply to every EVM token contract except Tempo and Hedera, whose chain-native tokens handle batching and compliance through their own mechanisms:

* **Batch transfers** — `multiTransfer(address[] recipients, uint256[] values)` sends to multiple recipients in one transaction.
* **Compliance blocklist** — the contract owner maintains an on-chain `isBlocked` list (`BlockPlaced` and `BlockReleased` events). Blocked addresses can't send tokens, and blocked callers can't invoke `transferFrom` or the [EIP-3009](https://docs.usdt0.to/technical-documentation/token-features/eip-3009.md) transfer functions.
* **No transfers to the token contract** — transfers with the token contract itself as the recipient revert, which prevents a common cause of lost funds.
* **Upgradeable** — tokens sit behind upgradeable proxies (ERC-1967, or the canonical Matic proxy on Polygon PoS). Implementations change through upgrades. For how upgrades are communicated, see the [Legacy Mesh upgrade notice](https://docs.usdt0.to/technical-documentation/developer/.md#4-legacy-mesh-usdt0-specific).
