Creates an unsigned TRX transfer transaction on the node side. If the recipient account is not activated, this transaction activates it.

Notes

• If the recipient account is not activated, this TRX transfer activates that account. Include activation cost in resource budgeting for batch withdrawals or new-address distribution.
• A transaction memo increases transaction size and Bandwidth consumption. Production systems should not use the memo as the only business identifier.
• When using Account Permission Management, Permission_id in the transaction must match the signing permission that will be used.
• Do not wait too long between construction and broadcast. Transactions expire, and expired transactions must be rebuilt and signed again.
• Use TransferAsset for TRC-10 transfers. Use TriggerSmartContract for TRC-20 transfers and other smart-contract calls.

Related resources

• BroadcastTransaction — broadcast the transaction after signing
• API signature and broadcast flow — end-to-end signing and broadcast workflow
• Transaction protocol — TAPOS, expiration, and raw_data structure
• Accounts — account activation and address derivation