TronLink Setup

Learn how to configure the CatFee Seamless Energy node in TronLink or similar TRON wallets that support custom nodes, and complete the first broadcast test.

If the wallet supports custom TRON nodes or broadcast nodes, you can configure the dedicated Seamless Energy domain provided by CatFee as the broadcast address. The wallet still signs locally using its original flow, and CatFee only handles the signed transaction broadcast flow.

Wallet UI labels may differ between versions, but the core idea is the same: find the network or node settings and replace the broadcast domain with the dedicated node domain provided by CatFee.

Prerequisites

• A Seamless Energy node has been applied for in the CatFee User Center.

• The node access domain has been obtained.

• You have chosen bound address or API KEY authentication.

• If using bound address, the wallet address that sends the transaction, meaning the owner address in the transaction, has already been bound in the User Center.

Steps

1. Open wallet network or node settings

In TronLink, find the entry related to network, node, custom node, or developer settings. Different clients may use different names, but they must allow changing the broadcast target node.

Do not fill the node domain into these fields:

• Recipient address.

• Memo.

• Token contract address.

• Contact address book.

2. Fill in the Seamless Energy node domain

Configure the node address as:

https://{NodeSlug}.catfee.vip

If the wallet asks for Host, URL, or Endpoint, enter the full domain.

If the wallet distinguishes Full Node, Solidity Node, and Event Server, confirm the setting related to broadcasting first. Do not mistakenly fill the Seamless Energy node into a field unrelated to broadcasting.

3. Confirm the authentication method

• Bound address mode: no additional key needs to be stored. The owner address in the transaction only needs to be bound.

• The owner address means the wallet address that initiates the transaction.

• API KEY mode: suitable only when the wallet supports custom headers or additional authentication information.

• No-authentication mode: recommended only for temporary verification.

For ordinary wallet users, bound address mode is usually recommended.

4. Send a small contract transaction

Test one of the following scenarios first:

• Small TRC20 transfer.

• Token approval.

• Test environment or low-risk contract call.

Regular TRX transfers or account operations do not purchase ENERGY and are forwarded directly.

Verification result

After configuration succeeds, the wallet should keep its original signing flow unchanged, while the broadcast target becomes the CatFee Seamless Energy node. Supported contract transactions will complete ENERGY estimation and resource preparation before broadcast.

The easiest user-side results to observe are:

• TRC20 transfer or approval transactions can still be initiated through the original flow.

• Regular TRX transfers do not additionally trigger ENERGY preparation.

• The wallet does not need to save private keys to CatFee.

Common questions

The wallet supports custom nodes but not custom Headers. What should I do?

Prefer bound address mode. This avoids passing CF-NODE-KEY on the wallet side.

The wallet does not have a custom node entry. What should I do?

This type of wallet usually needs to wait for official wallet integration, or you can relay broadcast requests through your own backend.

Why did a regular TRX transfer not trigger ENERGY purchase?

Because Seamless Energy only prepares ENERGY for supported contract transactions. Regular TRX transfers are non-contract transactions and are forwarded directly.

Next steps

• Other clients: Other Wallets and Apps.

• Backend integration: Application Integration.

• Risk control recommendations: Security.