Before sending USDT on Ethereum

□ 1. Confirm the asset and network

USDT exists on multiple networks. Confirm the recipient supports USDT on Ethereum mainnet before using these Ethereum-specific tools. A matching address format does not establish network support.

ChainKit: https://first-fold-launch.foggyibis16.chatgpt.site/

□ 2. Compare the full recipient address

Use a trusted source, compare every character, and recheck the wallet confirmation. A checksum is useful for text mistakes; it does not prove ownership or stop a substituted valid address.

ChainKit: https://first-fold-launch.foggyibis16.chatgpt.site/

□ 3. Read what the request actually asks

A token transfer and a token allowance are different operations. CallLens reads only supported static layouts; selectors are not unique and output is not a simulation.

CallLens: https://call-lens.foggyibis16.chatgpt.site/

□ 4. Review every payout row

Look for duplicates, misplaced decimals, wrong-network declarations and excluded error rows. PayoutCheck includes duplicates in the warning-bearing subtotal; it does not approve or send the batch.

PayoutCheck: https://payout-check.foggyibis16.chatgpt.site/

□ 5. Keep payment requests and receipts separate

Verify the recipient and amount through a trusted channel. PayNote links are unsigned, editable requests. A QR or a screenshot is not evidence of funds received.

PayNote: https://pay-note.foggyibis16.chatgpt.site/

□ 6. Budget Ethereum fees in ETH

Use your wallet’s current gas estimate. GasBench translates your inputs into fee arithmetic; it does not predict inclusion or execution. Failed executions may still cost gas.

GasBench: https://gas-bench.foggyibis16.chatgpt.site/

□ 7. Verify the transaction independently

Review the final wallet screen. After sending, inspect the correct-network transaction and asset receipt in your own trusted wallet or explorer. Never give these tools a seed phrase, private key or password.