Handling Tron data

The Tron query builder exposes transactions, event logs, internal transactions, and block headers. Filters and returned fields use the same formats as the Tron Portal API.

Address and hex formats

Tron Portal hex strings are bare, without 0x.

Transaction filters and fields use 21-byte addresses beginning with 41, for example 41a614f8....
Log filters and log.address use the lower 20 bytes, without 41, for example a614f8....
Log topics are 32-byte ABI words. An indexed address occupies the final 20 bytes.

Using the 41... USDT address in a log filter returns no matches. Use the 20-byte form for addLogRequest().

Decode TRC-20 transfers

TRC-20 logs use the same ABI event layout as ERC-20 logs, but the hex strings are not 0x-prefixed. Decode them explicitly:

import { tronQuery } from '@subsquid/pipes/tron'

const USDT = 'a614f803b6fd780986a42c78ec9c7f77e6ded13c'
const TRANSFER_TOPIC = 'ddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef'

export const usdtTransfers = tronQuery()
  .addFields({
    block: { number: true, timestamp: true },
    log: { transactionIndex: true, logIndex: true, topics: true, data: true },
  })
  .addLogRequest({
    range: { from: 84_000_000 },
    request: { address: [USDT], topic0: [TRANSFER_TOPIC] },
  })
  .build()
  .pipe((blocks) =>
    blocks.flatMap((block) =>
      block.logs.flatMap((log) => {
        if (!log.data || !log.topics?.[1] || !log.topics[2]) return []

        return [{
          block: block.header.number,
          timestamp: block.header.timestamp,
          from: `41${log.topics[1].slice(-40)}`,
          to: `41${log.topics[2].slice(-40)}`,
          amount: BigInt(`0x${log.data}`),
        }]
      }),
    ),
  )

evmEventDecoder() cannot be reused for these logs because EVM Portal data uses 0x-prefixed hex.

Transaction request families

Method	Data selected
`addTransactionRequest()`	Transactions filtered by contract `type`.
`addTransferTransactionRequest()`	Native TRX transfers.
`addTransferAssetTransactionRequest()`	TRC-10 asset transfers.
`addTriggerSmartContractTransactionRequest()`	Smart-contract calls filtered by owner, contract, or method selector.
`addLogRequest()`	TVM event logs.
`addInternalTransactionRequest()`	Contract-internal calls and value movements.

Transaction request methods accept logs: true and internalTransactions: true. Log and internal-transaction requests accept transaction: true. Join the returned collections with transactionIndex.

Value types

Transaction amounts and resource fields such as feeLimit, fee, energyUsageTotal, and netFee are bigint. The wire values are signed decimal strings.
Block and transaction timestamps are Unix milliseconds represented as number.
parameter, ret, and callValueInfo are raw JSON. Their shapes depend on the transaction type.

See the query builder reference for the complete field and filter list.

Pipes SDK

Tron - Squid SDK

Address and hex formats

Decode TRC-20 transfers

Transaction request families

Value types

​Address and hex formats

​Decode TRC-20 transfers

​Transaction request families

​Value types

Address and hex formats

Decode TRC-20 transfers

Transaction request families

Value types