FAQ

Common statuses, error causes, resource handling boundaries, and broadcast behavior for CatFee Seamless Energy integration, for quick troubleshooting by wallets and developers.

Do I need to replace the entire TRON node or only the broadcast node?

In most cases, what you need to confirm most is where the signed transaction is finally broadcast. The core function of Seamless Energy happens at the broadcast stage.

If your wallet or application binds query, transaction construction, and broadcast to the same node configuration, you can also switch the whole node configuration to the Seamless Energy node. But conceptually, the key point is the broadcast entry point.

Why do regular TRX transfers look unchanged after I changed the node?

This is normal. Regular TRX transfers do not trigger ENERGY preparation. Seamless Energy mainly handles contract transactions, such as TRC20 transfers, approvals, and other contract calls.

What does "node domain does not exist" mean?

It usually means the node access domain is typed incorrectly, or the node has been deleted. First check the domain spelling and confirm that the node still exists in the CatFee User Center.

What should I do if the node is disabled?

The node domain cannot continue broadcasting transactions while disabled. Re-enable it in the CatFee User Center first, then send the request again.

What happens when the member balance is insufficient?

It depends on the insufficient balance policy you configured:

• Continue broadcast: skip ENERGY purchase and continue forwarding the original transaction.

• Stop broadcast: return 402 PAYMENT_REQUIRED and do not broadcast the original transaction.

Why did CatFee not continue broadcasting the original transaction after ENERGY purchase failed?

If ENERGY estimation, resource order creation, or energy transaction broadcast fails, CatFee does not continue forwarding the original transaction. This avoids putting the transaction on-chain when resources are not ready.

The only exception is: the member balance is insufficient and you explicitly configured "continue broadcast".

Why do regular TRX transfers not purchase ENERGY?

Regular TRX transfers, account operations, and other non-contract transactions do not purchase ENERGY. They are forwarded directly to CatFee's TRON node.

Do normal query requests automatically purchase ENERGY?

No. Querying accounts, blocks, transactions, and other read requests does not trigger resource preparation. Seamless Energy's enhancement logic happens when signed transactions are broadcast.

Which transactions are currently supported?

Current ENERGY handling only targets transactions whose first contract is TriggerSmartContract.

Why can a transaction still fail after resources are prepared successfully?

Successful resource preparation only means ENERGY has been prepared as much as possible. It does not guarantee that contract execution will succeed. Contracts may still fail for reasons such as:

• Business conditions not met.

• Account balance insufficient.

• Approval allowance insufficient.

• Contract logic reverted.

• TRON network conditions fluctuating.

Why does CatFee wait about 2 seconds before forwarding the original transaction?

TRON does not support nonce queue semantics and does not have a bundle mechanism for packaging transactions together. This wait is intended to help resources arrive first before broadcasting the original transaction.

What does "requests too fast" mean?

The node has request frequency limits. When the limit is exceeded, requests are rejected. Reduce concurrency or sending rate, and evaluate whether a more suitable node plan is needed based on your business scale.

Can I give my private key to CatFee and let the platform sign for me?

No. CatFee only handles the broadcast flow of signed transactions. It does not custody user private keys and cannot sign on behalf of users.

Next steps

• First-time integration: Quick Start.

• Server-side integration: Application Integration.

• AI-assisted refactoring: AI-Assisted Integration.

• Manual wallet configuration: Wallet Settings.