0x06fdde03 (name), 0x95d89b41 (symbol), 0x313ce567 (decimals), and 0x18160ddd (totalSupply) work identically — only the resource model differs.eth_call and reports all three back. Useful when you need the EVM form for a direct contract call.They don't — at the ABI level. TRC-20 inherits Ethereum's ERC-20 interface (name, symbol, decimals, totalSupply, balanceOf, transfer, approve). The same selector bytes work; the differences are deployment fees and resource model (energy/bandwidth vs gas).
Tether chose 6 decimals for USDT on every chain it deploys to — Ethereum, TRON, Solana, Avalanche. That keeps the integer representation consistent: 1 USDT = 1,000,000 raw units regardless of network.
In theory yes — both are 20-byte hashes. In practice the deployment contexts differ enough that collisions are vanishingly rare. But always verify the chain before you send: cross-chain pastes are an easy way to lose funds.
Either the address is not a contract, the contract doesn't implement TRC-20's standard reads, or the public TRON RPCs are rate-limiting. The server-side cache mitigates the third case for popular tokens.