TronBox

You can deploy your contracts to various networks using the tronbox migrate command with the --network flag. The MetaCoin project supports the following networks:

• Mainnet: mainnet (https://api.trongrid.io)
• Shasta Testnet: shasta (https://api.shasta.trongrid.io). Obtain test coins at https://shasta.tronex.io/
• Nile Testnet: nile (https://nile.trongrid.io). Obtain test coins at https://nileex.io/join/getJoinPage
• Localnet: Default (http://127.0.0.1:9090). Uses the TronBox Runtime Environment (TRE).

# Deploy to Mainnet
tronbox migrate --network mainnet

# Deploy to Shasta Testnet
tronbox migrate --network shasta

# Deploy to Nile Testnet
tronbox migrate --network nile

# Deploy to Localnet
tronbox migrate

Create a new project structure by running tronbox init. This command generates the following directory structure:

• contracts/: Directory for Solidity contracts.
• migrations/: Directory for scriptable deployment files.
• test/: Directory for test files for testing your application and contracts.
• tronbox-config.js: TronBox configuration file.

$ tronbox init

Install the TronBox CLI globally using npm to begin developing smart contracts for the TRON Virtual Machine (TVM).

$ npm install -g tronbox

When initializing init with { evm: true }, the wrapper attaches an _ethers object to the returned instance. This object provides access to the ethers library, a provider, and signers, enabling developers to use standard Ethers.js patterns on the TRON network.

Key properties on tronWrap._ethers:

• provider: The ethers.JsonRpcProvider instance.
• getSigner(address): Returns an EthersSignerProxy for the specified address.
• getSigners(): Returns an array of all available signers as EthersSignerProxy instances.

const tronWrap = init(options, { evm: true });
const signer = tronWrap._ethers.getSigner(address);
// Use signer with standard ethers.js methods

The ConsoleLogger utility is used to extract and format console.log output from Tron transactions. It works by inspecting the internal_transactions of a transaction for calls made to the special CONSOLE_ADDRESS (41000000000000000000636f6e736f6c652e6c6f67).

When a match is found, the logger uses the transaction data to identify the function signature (via its hash), determines the expected parameter types, and decodes the hex data into human-readable values (converting address to standard formats and uint256/int256 to strings).

When a compilation is successful, the returnVal object contains contract definitions keyed by the contract_name. Each definition includes:

• contract_name: The name of the contract.
• sourcePath: The original path to the source file.
• source: The raw source code.
• sourceMap: The EVM bytecode source map.
• deployedSourceMap: The deployed bytecode source map.
• abi: The Application Binary Interface.
• bytecode: The compiled bytecode (prefixed with 0x).
• deployedBytecode: The deployed bytecode (prefixed with 0x).
• unlinked_binary: The unlinked binary (deprecated).
• compiler: An object containing name (e.g., 'solc') and version.

The tronWrap instance maintains a networkConfig object derived from the initialization options. This object is used to resolve transaction parameters like feeLimit, originEnergyLimit, and callValue.

When performing operations, the wrapper resolves options in the following priority:

1. Explicitly provided txOptions (e.g., in a contract call).
2. The networkConfig derived from the initial init() call.
3. Default constants defined in the project.

Supported configuration keys include:

• fullNode / fullHost
• feeLimit / fee_limit
• originEnergyLimit / origin_energy_limit
• callValue / call_value
• tokenValue / token_value
• userFeePercentage / consume_user_resource_percent