Skip to main content

Tron (TRX)

Tron wallet structure​

A Tron wallet has the following structure.

  • Main address
  • Fee address
  • Child address

TIP The fee address is used to inject the fee (TRX) required for gathering tokens in a centralized wallet into child addresses, or to inject the fee (TRX) into child addresses as needed.






Deposit​

Deposit status​

When an asset sent from the outside arrives at the main address or a child address, Octet recognizes it as a deposit. However, the deposit is not processed as completed even if the deposit transaction is included in a block. To ensure the finality of the transaction, additional blocks must be generated before the transaction is processed as completed (FINALIZED). When an asset is sent from the outside but has not arrived at the main address or a child address, that transaction is not recognized. Therefore, there is no failed (FAILED) status for deposit transactions.

Status nameDescription
UNFINALIZEDDeposit transaction is included in a block
FINALIZEDDeposit transaction is included in a block and the next block is generated




Gathering​

Gathering is only available in centralized wallets.

Gathering process​

Assets stored in child addresses do not move to the main address until gathering is requested. Therefore, you should gather regularly to avoid a deficit in the main address.

When gathering of a specific asset is requested, the TRX or tokens stored in every child address are transferred to the main address. At this point, one transaction occurs per child address. For example, if TRX is stored in 10 child addresses, 10 transactions occur in total.

However, if a gathering is already in progress for a specific child address, a new gathering cannot be requested. The gathering in progress must be completed before a new gathering can proceed.

Activate the main address before gathering.

Gathering can only proceed to an activated main address. Before gathering, you must first check that the main address is activated.


1. Gathering TRX​

A TRX gathering fee occurs once per transaction. Bandwidth Points (BP) are used as the fee, and when the available BP is exhausted, TRX is used as the fee. This is deducted from the assets to be gathered. At this point, gathering does not proceed for child addresses whose assets to be gathered are less than the estimated fee. The gathering process is as follows.

  1. Request gathering.
  2. A transaction is created for each child address to be gathered.
  3. The optimal fee is calculated and the transaction is propagated.
  4. The gathering is completed when the transaction is included in a block.

2. Gathering TRC-10​

A TRC-10 gathering fee occurs once per transaction. Bandwidth Points (BP) are used as the fee, and when the available BP is exhausted, TRX is used as the fee. At this point, if the child address has no TRX to pay the fee, TRX is injected from the fee address into the child address. A fee (fee injection cost) occurs in this process as well. The child address pays the fee with the received TRX and proceeds with the gathering. The gathering process is as follows.

  1. Request gathering.
  2. If BP is exhausted, TRX to be used as the gathering fee is injected from the fee address into the child address.
  3. A transaction is created for each child address to be gathered.
  4. The optimal fee is calculated and the transaction is propagated.
  5. The gathering is completed when the transaction is included in a block.

3. Gathering TRC-20​

A TRC-20 gathering fee occurs once per transaction. Bandwidth Points and Energy are used as the fee, and when the available Bandwidth Points or Energy is exhausted, TRX is used as the fee. At this point, if the child address has no TRX to pay the fee, TRX is injected from the fee address into the child address. A fee (fee injection cost) occurs in this process as well. The child address pays the fee with the received TRX and proceeds with the gathering. The gathering process is as follows.

  1. Request gathering.
  2. If BP or Energy is exhausted, TRX to be used as the gathering fee is injected from the fee address into the child address.
  3. A transaction is created for each child address to be gathered.
  4. The optimal fee is calculated and the transaction is propagated.
  5. The gathering is completed when the transaction is included in a block.


Gathering fees​

A gathering fee occurs once per transaction.

  • When gathering TRX: the fee is deducted from the address where the transaction occurs.
  • When gathering tokens: the fee is deducted from the address where the transaction occurs. However, if that address has no TRX to use as the fee, it receives assets to use as the fee from the fee address and then uses them.


Gathering status​

Gathering status is divided into seven statuses depending on the gathering process. Assets stored in child addresses are in awaiting gathering (AWAITING_GATHERING) status.

If a fee injection is required when gathering is requested, the asset status changes to awaiting fee injection (AWAITING_FEE_INJECTION). When the fee injection transaction is created, the asset status changes to fee injecting (FEE_INJECTING). If the fee injection fails, the asset status is processed as fee injection failed (FEE_INJECTION_FAILED).

When the fee injection succeeds and a gathering transaction is created, the asset status changes to gathering (GATHERING). When the transaction is included in a block, the asset status is processed as gathering completed (COMPLETED) and the gathering is finished.

When gathering is attempted but the transaction fails, the asset status remains as gathering failed (GATHERING_FAILED). Assets in fee injection failed or gathering failed status are included in the gathering targets again. When gathering is attempted but the transaction could not be created due to insufficient fees, it remains in awaiting gathering (AWAITING_GATHERING) status.

Status nameDescription
AWAITING_GATHERINGAwaiting gathering
AWAITING_FEE_INJECTIONAwaiting fee injection
FEE_INJECTINGFee injecting
FEE_INJECTION_FAILEDFee injection failed
GATHERINGGathering transaction created
COMPLETEDGathering transaction completed
GATHERING_FAILEDGathering transaction failed




Withdrawal​

Withdrawal status​

Unlike deposits, a withdrawal is processed as withdrawal completed (FINALIZED) as soon as the transaction is included in a block.

Status nameDescription
AWAITING_DECISIONAwaiting withdrawal approval
REJECTEDWithdrawal is rejected
AWAITING_WITHDRAWALWithdrawal is approved and awaiting withdrawal
PENDINGWithdrawal transaction is created
FINALIZEDWithdrawal transaction is included in a block
FAILEDWithdrawal transaction failed



Balance lookup criteria​

You can check the balance of the assets stored in a specific address by calling the Get Address Balance API. The balance returned is divided into total balance and liquid balance.

  • Total balance means all assets with a confirmation of 1 or more.
  • Liquid balance means the assets that can be gathered or withdrawn. The liquid balance of a child address means the assets that can be gathered, and the liquid balance of the main address means the assets that can be withdrawn.





Fees​

Bandwidth Points (BP)​

BP is used as the fee when sending a transaction. Each address receives 600 BP for free every day. If BP is insufficient, TRX is automatically used to pay the fee.

BurnedTRX = Bandwidth Consumed x the unit price of Bandwidth

Energy​

Energy is used as the fee when executing transactions such as TRC-20 transfers. If Energy is insufficient, TRX is automatically used to pay the fee.

BurnedTRX = Energy quantity x the unit price of Energy