> For the complete documentation index, see [llms.txt](https://docs.luganodes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luganodes.com/tron-energy/faq.md).

# FAQ

Answers on delegation, integration and edge cases.

## The product

<details>

<summary>What is TRON Energy?</summary>

TRON Energy by Luganodes delegates energy to your sending addresses, so your TRON transactions run on delegated energy instead of burning TRX: on demand through the API or the RPC endpoint, or as a standing allocation on fixed addresses. See [Overview](https://docs.luganodes.com/tron-energy/overview.md).

</details>

<details>

<summary>What is energy on TRON?</summary>

Energy is the resource TRON uses to execute smart contracts, including token transfers, cross-chain swaps and other contract calls. It comes from staking TRX or receiving delegated resources. There is no free daily energy allowance; without enough energy, the network burns TRX to cover the shortfall. [How TRON fees work](https://docs.luganodes.com/tron-energy/how-tron-fees-work.md) explains the model.

</details>

<details>

<summary>Where does the energy come from?</summary>

Exclusively from institutional suppliers subject to strict compliance requirements, including TRX that our staking clients stake with Luganodes' TRON Super Representative, running since 2022. No anonymous energy sources are involved. Every delegation is recorded on-chain, so the source of the energy behind your transactions is always traceable. See [Compliance and screening](https://docs.luganodes.com/tron-energy/compliance-and-screening.md).

</details>

<details>

<summary>Does anything change in how we sign or send?</summary>

With the RPC endpoint and direct delegation, no: TRON applies delegated energy at the protocol level, and your wallet software, signing flow and custody setup stay the same. With the API, you sign the transaction first, create the rental and broadcast inside the 10-second window; the [Quickstart](https://docs.luganodes.com/tron-energy/energy-rental-api/quickstart.md) shows the order. In every model, your address signs nothing to receive the delegation.

</details>

<details>

<summary>Why does energy use vary by transaction?</summary>

Energy depends on the contract and the call. A cross-chain swap or multi-step contract call can consume more than a simple token transfer, and a USDT transfer to an address with a zero USDT balance consumes roughly twice the energy of one to an existing holder. We size your delegation to your actual transaction mix.

</details>

<details>

<summary>What if we use more than our delegated capacity?</summary>

TRON burns TRX from your sending address to cover the shortfall. If the address has no TRX, the transaction fails. Consumption monitoring and top-ups are available on request to help capacity keep pace with demand. See [Direct delegation](https://docs.luganodes.com/tron-energy/direct-delegation.md#capacity).

</details>

## Integration

<details>

<summary>Do you offer an API?</summary>

Yes, the on-demand API is live. Your system calls it before broadcasting a transaction, and we delegate the required energy to the sending address within a single block. Start with the [Quickstart](https://docs.luganodes.com/tron-energy/energy-rental-api/quickstart.md).

</details>

<details>

<summary>Can we route transactions through your RPC endpoint?</summary>

Your system sends signed transactions to the Luganodes enterprise-grade TRON RPC endpoint in place of its current node. For each contract call, we screen it, deliver the energy it needs to the sending address, then send it. Other transactions are sent to the node as they are. The RPC route comes at no additional cost: there is no charge for the endpoint itself. See [RPC endpoint](https://docs.luganodes.com/tron-energy/rpc-broadcast.md).

</details>

<details>

<summary>What if we miss the 10-second window?</summary>

The energy is reclaimed when the window closes. A transaction broadcast after that uses the sending address's own resources and burns TRX for any shortfall, or fails if the address holds no TRX. Create a new rental and broadcast as soon as it is `active`. See [Rental lifecycle](https://docs.luganodes.com/tron-energy/energy-rental-api/rental-lifecycle.md).

</details>

<details>

<summary>Does the sending address need TRX?</summary>

Delegated energy covers the energy a transaction needs. Bandwidth beyond the free daily allowance of 600, memo fees and multi-signature fees are paid in TRX from the sending address, and so is any energy shortfall. If the address has no TRX for these, the transaction fails. On top of energy, we can also cover bandwidth and account activation. Contact us to add them.

</details>

<details>

<summary>Do memos or multi-signature transactions cost extra?</summary>

Yes. On TRON, a memo and a multi-signature transaction each carry a separate 1 TRX fee. Send with a single signature and an empty memo where you can.

</details>

<details>

<summary>Can energy be delegated to a smart contract address?</summary>

No. The sending address must be a wallet address; a contract address returns `422 RECEIVER_IS_CONTRACT`.

</details>

<details>

<summary>Our address has only ever received USDT. Why is the rental refused?</summary>

An address that has only received tokens is not yet activated on chain, so it returns `422 RECEIVER_NOT_ACTIVATED`. Set `activate_if_needed: true` on the rental, or call [Activate an address](https://docs.luganodes.com/tron-energy/energy-rental-api/activate-an-address.md) first.

</details>

<details>

<summary>A queued rental outlasted our transaction's expiry. What should we do?</summary>

TronWeb and most TRON libraries set a transaction to expire 60 seconds after it is built. For rentals that may queue, sign with a longer expiration, or sign again once the rental is `active`. See [Rental lifecycle](https://docs.luganodes.com/tron-energy/energy-rental-api/rental-lifecycle.md#queued-requests).

</details>

<details>

<summary>How do we reconcile delegations with our transfers?</summary>

[List rentals](https://docs.luganodes.com/tron-energy/energy-rental-api/list-rentals.md) returns each rental with its delegation and reclaim transactions, and [Get usage](https://docs.luganodes.com/tron-energy/energy-rental-api/get-usage.md) returns daily totals.

</details>

## Still need help?

Email <business@luganodes.com> and include the `request_id` from any error.
