Download the PHP package iexbase/tron-api without Composer

TronAPI 6.0

TronAPI 6.0 is a strictly typed PHP 8.4 SDK for TRON FullNode, SolidityNode, JSON-RPC, smart contracts, tokens, staking, governance, indexed data, local signing, and hierarchical wallets.

Version 6.0 is a complete architecture rewrite. It is not source-compatible with 5.x. The new API deliberately removes global address/private-key state, floating-point asset values, duplicated route logic, and any native-service dependency on TronGrid.

The default dependency resolution uses Guzzle 8. Applications whose ecosystem still requires the current Guzzle 7 line can use it without replacing the TronAPI transport API.

Requirements

• PHP 8.4 on a 64-bit platform.
• Extensions: bcmath, ctype, curl, filter, gmp, hash, json, and mbstring.
• Composer 2.

Install the package without bypassing platform checks:

Quick start

The public-network profiles use TronGrid as the default hosted endpoint and indexer adapter. The SDK core is not coupled to it. A local FullNode, a separate SolidityNode, another JSON-RPC server, and any custom indexer can be composed independently:

jsonRpcUri is the complete endpoint. Use the dedicated port root for a self-hosted java-tron node (for example http://full-node.internal:8545) or the provider's exact path when it exposes JSON-RPC through a gateway.

See Node providers for role routing and custom adapter contracts.

Exact values and addresses

TRX values are never represented by float. Amount stores an exact non-negative decimal count of sun and converts decimal text without precision loss:

Address accepts checksum-verified Base58Check, 21-byte TRON hex, or explicit 20-byte ABI/EVM hex. Conversion never relies on an external node.

Safe transaction lifecycle

A state-changing service builds a transaction and approves its local TransactionIntent only after the returned node payload is checked against the requested owner, recipient/contract, amount, token ID, permission, memo, and fee limit. The SDK also reconstructs the official protobuf Transaction.raw bytes and requires an exact match with raw_data_hex, so displayed JSON cannot hide a different payload. Signing occurs locally and broadcasting is a separate explicit action.

Imported transactions have no trusted local intent and therefore require an explicit TransactionIntent before signing. Permission-aware multisignature workflows use the same verifier and append signatures immutably.

Before signing, estimateBandwidth() calculates the official protobuf size for the expected signature count. maximumBandwidthBurn() combines it with $tron->network()->bandwidthUnitPrice(); the result deliberately excludes available staked/free resources, Energy, account activation, memo, multisignature, and other operation-specific fixed fees.

Hierarchical wallets and message signatures

The wallet module implements BIP-39, BIP-32, the TRON BIP-44 path m/44'/195'/account'/change/index, xprv/xpub import/export, and public-only non-hardened address derivation.

Recovery phrases, passphrases, private keys, xprv chain codes, and provider API keys are redacted from debugger output. Private signers and wallet objects reject serialization. See Security model.

Smart contracts and tokens

The ABI subsystem supports overloaded functions, constructors, nested tuples, fixed/dynamic arrays, signed and unsigned integers, bytes, strings, addresses, return values, custom errors, revert reasons, anonymous events, and indexed log topics. Solidity aliases are expanded to their canonical types before selector hashing, and recursive encoded data is bounded before allocation. Complete calldata can be resolved by its four-byte selector and decoded with ContractService::decodeFunctionCall().

Typed contract services provide:

• constant calls through confirmed or latest state;
• Energy estimation and state-changing trigger transactions;
• deployment with constructor arguments, fee limit, call value, token value, origin Energy limit, and resource percentage;
• ABI replacement/removal and contract resource settings;
• TRC-20, TRC-721, and TRC-1155 wrappers;
• receipt event decoding and provider-neutral indexed event queries.

Runnable examples are documented in examples/README.md, including local key generation, balances, contract reads/writes, deployment, token standards, ABI events, and revert decoding.

Service map

The complete coverage map is documented in API coverage.

Examples

Every example is executable and defaults to Shasta for read operations. Any broadcast requires TRON_BROADCAST=1; transaction examples read private keys only from the environment and never send them to a node. Examples 01 and 18 print newly generated local private/public values for direct inspection.

The numbered examples cover:

1. local account/private-key generation, addresses, and exact amounts;
2. accounts, blocks, and network information;
3. custom node topology;
4. build, verify, sign, and optionally broadcast;
5. multisignature permissions;
6. TRC-10;
7. Stake 2.0;
8. contract reads;
9. contract writes;
10. contract deployment;
11. ABI function calldata and event decoding;
12. TRC-20, TRC-721, and TRC-1155;
13. provider-neutral indexed history;
14. JSON-RPC;
15. witnesses and governance;
16. native exchanges and market orders;
17. low-level/current-future endpoint access and active shielded TRC-20 routes;
18. BIP-39/BIP-32/xprv/xpub wallets and local key output;
19. Message Signature V2.

Documentation

• Architecture
• API coverage
• Node providers
• Security model
• Migration from 5.x

The protocol reference used by this project is the official TRON developer documentation, current java-tron HTTP API implementation, and TronWeb interoperability behavior.

Development and verification

composer check runs syntax validation, PHPStan at maximum level, and the full PHPUnit suite. Network-independent tests use deterministic transports and official protocol vectors; they never broadcast funds.

License

TronAPI is released under the MIT License.

Copyright (c) 2018-2026 iEXBase.