TVM Opcode Reference
The full list of TVM opcodes and their Energy costs is documented in the TRON Developer Hub at developers.tron.network.
Concept Mapping
This page is a precise, one-to-one mapping for developers and advanced users arriving from other ecosystems. Where there is no direct equivalent, the functional difference is explained explicitly.
Ethereum / EVM → TRON
Section titled “Ethereum / EVM → TRON”Core Architecture
Section titled “Core Architecture”| Ethereum Concept | TRON Equivalent | Notes |
|---|---|---|
| Gas | Energy + Bandwidth | TRON splits the single Gas abstraction into two resources. Energy covers smart contract execution; Bandwidth covers simple transfers. |
| Gas Price | N/A | TRON has no gas price auction. Resource costs are protocol-set, not market-driven. |
| Gas Limit | Energy Limit | A transaction can set a maximum Energy consumption to prevent runaway execution. |
| Ether (ETH) | TRX | Native currency. Both are used for staking, fee payment, and governance. |
| Wei | Sun | Smallest unit. 1 TRX = 1,000,000 Sun. |
| Gwei | N/A | No equivalent. TRON fees are expressed in TRX or Sun directly. |
| EVM | TVM | The TRON Virtual Machine. Largely EVM-compatible at the opcode level, with TRON-specific precompiles. |
| Solidity | Solidity (TVM variant) | TRON uses a fork of Solidity. Most contracts compile with minor changes. Some EVM opcodes behave differently on TVM. |
| Proof of Stake | Delegated Proof-of-Stake (DPoS) | TRON uses 27 elected block producers (Super Representatives) rather than a large validator set. |
| Validators | Super Representatives (SRs) | The 27 addresses with the highest vote totals produce all blocks. |
| Staking | Stake 2.0 (Freeze) | On Ethereum, staking means running a validator. On TRON, staking (freezing) TRX grants resource credits and voting power — no node operation required. |
| Block Time | 3 seconds | vs. ~12 seconds on Ethereum post-Merge. |
| Finality | ~19 blocks (~57 seconds) | Ethereum achieves finality in ~12 minutes (2 epochs). |
| Mempool | Transaction Pool | TRON has a mempool, but with 3-second blocks, transactions clear very quickly. No priority fee mechanism exists for faster inclusion. |
Accounts
Section titled “Accounts”| Ethereum Concept | TRON Equivalent | Notes |
|---|---|---|
| Externally Owned Account (EOA) | Normal Account | User-controlled account with a private key. Functionally identical. |
| Contract Account | Smart Contract Account | Deployed code address with no private key. |
| Account Nonce | Reference Block | TRON does not use a sequential nonce. Transactions reference a recent block hash (TAPOS — Transaction As Proof Of Stake) to prevent replay attacks. |
| Account Abstraction (EIP-4337) | Multi-Sig Account | TRON has native multi-signature support with configurable threshold/weight, but no full EIP-4337 equivalent. |
| ENS (Name Service) | None | No canonical on-chain name service equivalent to ENS. Some wallets display labels, but they are off-chain. |
| CREATE2 | CREATE2 (TVM) | Available in TVM. Address derivation works identically to Ethereum. |
| Address Format | Base58Check (T-prefix) | The same private key produces a 0x address (Ethereum) and a T-address (TRON). |
Tokens
Section titled “Tokens”| Ethereum Standard | TRON Standard | Notes |
|---|---|---|
| ERC-20 | TRC-20 | Functionally identical. Same interface (transfer, approve, allowance, transferFrom). |
| ERC-721 | TRC-721 | Functionally identical. NFT standard. |
| ERC-1155 | TRC-1155 | Multi-token standard. Supported on TVM. |
| Native ETH transfer | TRX transfer (Bandwidth) | TRX transfers use Bandwidth (not Energy) and are protocol-level, not contract calls. |
| None | TRC-10 | TRON-native protocol-level tokens, not smart contracts. No EVM equivalent. Created and managed directly by the TRON network layer. |
DeFi Primitives
Section titled “DeFi Primitives”| Ethereum Pattern | TRON Pattern | Notes |
|---|---|---|
| Approve + TransferFrom | Approve + TransferFrom | Identical pattern. The approval attack surface is the same — see the Safety Watchlist. |
| Wrapped ETH (WETH) | Wrapped TRX (WTRX) | TRX must be wrapped into a TRC-20 token (WTRX) for use in AMM contracts, since TRX is not itself ERC/TRC-20 compliant natively. |
| Uniswap V2/V3 | SunSwap V2/V3 | SunSwap is a Uniswap fork deployed on TRON. Liquidity pools, AMM math, and LP tokens are structurally identical. |
| Aave / Compound | JustLend | Lending protocol on TRON. Uses a similar interest rate model and health factor mechanic. |
| USDC / USDT (ERC-20) | USDT / USDD (TRC-20) | Tether’s TRC-20 USDT is the dominant stablecoin on TRON by volume. Native USDC minting on TRON was discontinued in 2024–2025; USDD is TRON’s native decentralized stablecoin alternative. |
Development Tooling
Section titled “Development Tooling”| Ethereum Tool | TRON Equivalent | Notes |
|---|---|---|
| Hardhat / Foundry | TronBox | TronBox is the primary TRON development framework. Hardhat plugins for TRON exist but are less mature. |
| ethers.js | tronweb | The canonical TRON JavaScript SDK. API differs significantly from ethers.js — not a drop-in replacement. |
| web3.js | tronweb | Same. tronweb is the single standard library. |
| MetaMask | TronLink | Browser wallet extension. TronLink is purpose-built for TRON. |
| Remix IDE | Remix (TVM mode) | Remix supports TVM deployment. Switch the deployment environment to “Injected TronLink” or a TRON-specific RPC. |
| Infura / Alchemy | TronGrid | Tron’s managed API node service. Provides JSON-RPC compatible endpoints for TVM and TRON-specific HTTP API. |
| Tenderly | TRONSCAN Contract Verification | No full Tenderly equivalent. TRONSCAN provides contract verification, transaction tracing, and ABI decoding. |
| Etherscan | TRONSCAN | Block explorer, contract verification, token tracking, and approval management. |
| Sepolia / Goerli | Nile / Shasta | TRON maintains two public testnets: Nile (primary) and Shasta. Nile is the recommended testnet for current development. |
| Chainlink | WINkLink | TRON’s native decentralized oracle network. It provides highly reliable, tamper-proof data feeds (Price Feeds, VRF, OCR) natively built for the TRON ecosystem. |
Solana → TRON
Section titled “Solana → TRON”| Solana Concept | TRON Equivalent | Notes |
|---|---|---|
| SOL | TRX | Native currency. |
| Lamports | Sun | Smallest unit. 1 SOL = 10⁹ Lamports; 1 TRX = 10⁶ Sun. |
| Proof of History (PoH) | DPoS | Solana uses a verifiable delay function for ordering; TRON uses elected block producers with a 3-second slot. |
| Validators | Super Representatives | Solana has ~2,000+ validators; TRON has exactly 27 active SRs. |
| Rent | Account Activation (1 TRX) | Solana charges rent for on-chain storage; TRON charges a one-time 1 TRX activation fee for new addresses. No ongoing storage rent. |
| Programs | Smart Contracts (TVM) | Solana programs are stateless BPF bytecode; TRON smart contracts are stateful EVM-compatible bytecode. |
| SPL Token | TRC-20 | Fungible token standard. SPL and TRC-20 are architecturally different (Solana uses a shared token program; TRON deploys a contract per token). |
| Associated Token Account (ATA) | N/A | TRON does not require separate token accounts. TRC-20 balances are tracked within the contract’s storage, directly mapped to address. |
| Transaction Fees | Energy + Bandwidth burn | Solana pays a base fee + priority fee per transaction; TRON uses staked resources or TRX burn. |
| Compute Units | Energy | Solana measures instruction cost in Compute Units; TRON uses Energy for smart contract execution. |
| Anchor Framework | TronBox | Development frameworks for their respective ecosystems. |
| Phantom Wallet | TronLink | Primary ecosystem wallets. |
Move (Aptos / Sui) → TRON
Section titled “Move (Aptos / Sui) → TRON”| Move Concept | TRON Equivalent | Notes |
|---|---|---|
| APT / SUI | TRX | Native currency. |
| Gas | Energy + Bandwidth | Move chains use a single gas abstraction; TRON splits into two resources. |
| Resources (Move type) | Contract Storage | Move’s linear type system enforces that resources can’t be copied or dropped — this safety property has no direct TRON equivalent. TVM contracts manage storage manually. |
| Modules | Smart Contracts | Move programs are organized as modules published to addresses; TRON smart contracts are deployed independently to unique addresses. |
| Objects (Sui) | N/A | Sui’s object model has no equivalent on TRON. TRON uses account-based storage like Ethereum. |
| Fungible Asset (FA) | TRC-20 | The modern Move fungible token standard maps to TRC-20 in function. |
| Coin (Aptos) | TRC-20 | Aptos’s original token standard. |
| BCS Serialization | ABI Encoding | Move uses BCS for transaction encoding; TRON uses Ethereum ABI encoding for contract calls. |
| Staking | Stake 2.0 | Both ecosystems stake to validators/SRs for rewards. The mechanics differ significantly. |
| Move Prover | N/A | Move’s formal verification toolchain has no equivalent in the TVM ecosystem. |
tronweb API Reference
The tronweb library documentation covers all available methods for interacting with the TRON network programmatically.