Simply Replace Your Broadcast Endpoint

Connect by API or a custom wallet node. CatFee automatically prepares ENERGY and Bandwidth before broadcasting.

Seamless Energy enhances TRON transaction broadcasting; balance, block, and transaction queries can keep using the original node.

  • API integration
  • Wallet apps
  • Node authentication
  • Original transaction unchanged
Create Integration
View API DocsWallet Setup Guide
Developer APIHTTP / gRPC Send signed transactions
TronLinkWallet AppCustom node connection Supports TronLink
CatFee

CatFee

Dedicated broadcast node
Seamless Energy

Automatically prepare ENERGY and Bandwidth

Help reduce transfer costs

TRONTRON NetworkBroadcast to network

Wallet App Integration

Configure in 5 Steps and Use Seamless Energy Directly

Copy your dedicated node address and port, then configure it as a custom node in your wallet app.

View TronLink setup guide
Me
Preferences
Switch Node
Add Custom Node
Select Custom Node
Your dedicated node

Copy the details below and configure them in TronLink or another supported wallet.

your-catfee-dedicated-node.catfee.pro
50051

Your wallet confirms and signs first. The dedicated node then prepares resources and broadcasts the transaction unchanged.

Quick Integration

Go Live in 4 Steps

View API integration guide
01

Apply for a Node

Submit business details and receive node credentials.

02

Integrate

Configure a wallet node or connect over HTTP / gRPC.

03

Verify

Validate resource preparation and broadcasting with a test transaction.

04

Launch

Switch to production and run with reliable Seamless Energy.

Developer integration

Replace the node address and go

Replace the original TRON broadcast host with your CatFee node. Keep the path, request body, and transaction signature unchanged.

POST https://{NodeSlug}.catfee.vip/wallet/broadcasttransaction
Content-Type: application/json
CF-NODE-KEY: {AccessKey}

{
  "raw_data_hex": "...",
  "signature": ["..."]
}

Include CF-NODE-KEY when API key authentication is enabled; omit it for bound-address or unauthenticated modes.

Security & privacy

Three layers protect your business

Signing Boundary

Transactions are constructed and signed by your application or backend. CatFee never accesses private keys, seed phrases, or keystores, and never modifies the original transaction.

Node Authentication

Send CF-NODE-KEY through an HTTP header or gRPC metadata. The AccessKey belongs to the dedicated node and can be viewed or reset in the dashboard.

Supported Scope

The node is compatible with native TRON broadcast paths and currently focuses on signed transactions containing TriggerSmartContract. Other transactions follow the configured node strategy.

Why Developers Need It

Remove ENERGY Problems from the User Experience

Traditional Flow

Buy ENERGYSwitch platforms or call an order API
Wait for DeliveryPoll resources and confirmation
Broadcast AgainResubmit the original transaction

Seamless Energy

Signed TransactionYour application signs as usual
Prepare & BroadcastCompleted automatically by CatFee
On-chain ConfirmationThe original transaction reaches chain

Product Capabilities

One Broadcast Stack for Wallets and APIs

Once a transaction reaches your dedicated CatFee node, one shared stack handles interface compatibility, authentication, resource preparation, and broadcasting.

Compatible with Native TRON Broadcast APIs

Keep your existing paths, request formats, transaction signatures, and broadcast methods without rebuilding the transaction flow.

Dedicated Domain Replaces the Broadcast Entry

Use an isolated node domain: developers replace the broadcast host, while wallet apps connect through a custom node.

Multiple Authentication Modes Protect the Node

Support API keys, bound addresses, and business-specific authentication for node-level access isolation.

Traceable Failure Handling and Results

Return clear resource-preparation, broadcast, and on-chain results for troubleshooting and transaction tracking.

Scope: enhancement occurs during signed-transaction broadcasting. ENERGY handling currently focuses on the first TriggerSmartContract call; regular TRX transfers are forwarded directly, and read requests do not trigger resource preparation.

Transaction Control & Security

You Stay in Control of Every Transaction

Your wallet or business system constructs and signs each transaction. CatFee prepares resources and broadcasts within the configured permissions, keeping the process clear and verifiable.

View security guide

Your Wallet / App

Construct and confirm independently

Signing authority stays in your secure environment

CatFee

Prepare resources and broadcast as signed

Strictly follows the signed transaction content

TRON Network

Validate and confirm on-chain

Processing status and results remain visible

Independent signing · Original broadcast · Permission isolation · Visible results

Use Cases

Built for Developer Workflows

For developers and service providers that control the transaction broadcast endpoint and want ENERGY preparation handled automatically.

Wallet Apps (TronLink Recommended)

For TronLink and other wallet apps that support TRON transaction signing. After the user signs, the Seamless Energy node prepares resources and broadcasts automatically—without a separate energy purchase or wait.

Developers and Backend Services

Send CF-NODE-KEY through an HTTP header or gRPC metadata when managing large address sets.

Payment and Trading Systems

Add a stable ENERGY preparation and broadcast path for payments, merchant settlement, and frequent on-chain operations.

DApps, Bots, and Automation

Support TRC20 transfers, approvals, swaps, and other contract interactions that depend on ENERGY.

Wallet Providers

Use CatFee as an enhanced broadcast endpoint to reduce transaction failures caused by insufficient ENERGY.

Before You Integrate

Frequently Asked Questions

Review broadcast scope, supported transactions, node authentication, and exception handling. See the complete documentation for more troubleshooting guidance.

View complete FAQ
Yes. Seamless Energy acts during signed-transaction broadcasting. Balance, block, and transaction queries can keep using the original node; wallets that use one node for every request may switch the complete node configuration.

Ready to start

Add Seamless Energy with One Dedicated Broadcast Node

Apply for a node, obtain an AccessKey, replace the broadcast domain, add CF-NODE-KEY, and validate the integration with a small or testnet transaction.

Apply for a Dedicated Node
View Integration Guide