> For the complete documentation index, see [llms.txt](https://docs.catfee.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catfee.io/en/getting-started/seamless-energy.md). # Seamless Energy Seamless Energy is a TRON transaction broadcast enhancement service developed and operated by CatFee. Developers only need to broadcast **signed transactions** to the dedicated Seamless Energy node provided by CatFee. Before broadcasting the original transaction, CatFee automatically estimates the ENERGY required for the contract call, prepares resources for the transaction owner address, and then forwards the original transaction unchanged to CatFee's TRON node. Seamless Energy is built on CatFee's own TRON node service. For developers, it behaves like a dedicated node compatible with the original TRON broadcast APIs: in most cases, you only replace the broadcast domain, while keeping the original path and request body unchanged. ENERGY estimation and resource preparation are completed automatically before broadcasting. CatFee does not custody user private keys, cannot sign on behalf of users, and cannot modify the user's original transaction. Seamless Energy only handles the **broadcast flow for signed transactions**. If this is your first time learning about the product, you can think of it this way: **it is not a signing service or wallet custody service. It is a TRON broadcast entry point with automatic ENERGY preparation.** ## Who should use it * Developers who need to automatically prepare resources for TRC20 transfers, approvals, swaps, and other contract transactions. * Backend services that want to keep using the original TRON broadcast APIs and only replace the broadcast domain in most scenarios. * DApps or wallet teams that want to remove ENERGY purchase logic from the client side. * Wallet service providers, payment systems, or transaction relay services that want to reduce TRON contract transaction failure rates. ## Core capabilities * Dedicated node domain: each node has an independent access domain, for example `https://{NodeSlug}.catfee.vip`. * Original API compatibility: continue using the original TRON broadcast paths and request bodies. * Resource preparation before broadcast: identify supported contract transactions, estimate ENERGY, and prepare resources automatically. * Original transaction forwarded unchanged: CatFee does not change transaction content, re-sign, or replace the owner address. * Multiple authentication modes: no authentication, bound address, and API KEY. * Configurable balance policy: when the member balance is insufficient, you can choose to continue broadcasting or stop broadcasting. ## Which page should I read first * I am a developer or backend integrator: read [Quick Start](/en/getting-started/seamless-energy/quick-start.md), then [Application Integration](/en/getting-started/seamless-energy/application-integration.md). * I want AI to help me locate code and generate an integration plan: read [AI-Assisted Integration](/en/getting-started/seamless-energy/ai-assisted-integration.md). * I am on a wallet team or product team: read [Application Integration](/en/getting-started/seamless-energy/application-integration.md), then [Wallet Settings](/en/getting-started/seamless-energy/wallet-settings.md). * I am an ordinary wallet user: read [Wallet Settings](/en/getting-started/seamless-energy/wallet-settings.md). * I care most about private keys and security boundaries: read [Security](/en/getting-started/seamless-energy/security.md). ## Core concepts * Node domain: the dedicated access domain of each Seamless Energy node, for example `https://{NodeSlug}.catfee.vip`. * Seamless Energy node: the dedicated broadcast access node generated by CatFee for a member account. * AccessKey: a 41-character random access key generated for the node and passed through `CF-NODE-KEY`. * Original transaction: a TRON transaction signed locally by the wallet. CatFee only forwards it and does not modify it. * Energy transaction: the resource transaction broadcast by CatFee to prepare ENERGY for the original transaction owner address. * Insufficient balance policy: when the balance is insufficient, either continue forwarding the original transaction or return an insufficient balance error directly. * Owner address: the transaction sender address, meaning the wallet address from which the transaction is sent. ## Workflow 1. The wallet or backend constructs and signs the transaction locally. 2. The client broadcasts the signed transaction to the Seamless Energy node. 3. CatFee identifies the member node by domain and performs authentication. 4. If the transaction is a supported contract call, CatFee estimates ENERGY and creates a resource order. 5. After the energy transaction is broadcast successfully, CatFee waits about 2 seconds before forwarding the original transaction. 6. The original transaction is forwarded unchanged to CatFee's TRON node. 7. The client receives a response in the original TRON broadcast API format. ## What it handles and does not handle * It handles: the **broadcast stage** of signed transactions. * It automatically prepares ENERGY: for eligible contract broadcast transactions. * It does not handle: your private key, mnemonic phrase, or signing process. * It does not automatically purchase ENERGY: for regular TRX transfers, account operations, or other non-contract transactions. * It does not modify: addresses, amounts, or contract parameters in the original transaction. ## Authentication methods Seamless Energy nodes support three authentication methods: * API KEY: suitable for developers, wallet service providers, or businesses with many addresses. Requests must pass `CF-NODE-KEY: {AccessKey}` in the HTTP header or gRPC metadata, and the value must match the 41-character random `AccessKey` stored for the node. * Bound address: suitable for ordinary wallet users or clients that do not support custom headers. The owner address of the first transaction in the request must be bound to the node. * No authentication: suitable for temporary testing or scenarios where open access is explicitly required. The node domain is used to locate the node. Bound address or API KEY is used to confirm whether the request is authorized to use that node. ## Fees and limits * Each member account can create at most 1 Seamless Energy node. * The node can be enabled, disabled, or recreated in the User Center. * Only supported contract transactions trigger ENERGY estimation and resource preparation. * Non-contract transactions do not purchase ENERGY and are forwarded directly to CatFee's TRON node. * Variable fees, rate limits, and resource prices are subject to the actual display in the CatFee dashboard. ## Security boundaries * CatFee only receives signed transactions and does not need wallet mnemonic phrases, private keys, or keystore files. * CatFee cannot sign on behalf of users or modify the user's original transaction. * The node domain is a routing identifier and should not be used as the only security credential. * No-authentication mode exposes the node to anyone who knows the node domain. ## Next steps * To complete integration quickly: read [Quick Start](/en/getting-started/seamless-energy/quick-start.md). * To integrate a backend service or wallet: read [Application Integration](/en/getting-started/seamless-energy/application-integration.md). * To use AI to locate integration code: read [AI-Assisted Integration](/en/getting-started/seamless-energy/ai-assisted-integration.md). * To configure a node for wallet users: read [Wallet Settings](/en/getting-started/seamless-energy/wallet-settings.md). * To troubleshoot common errors: read [FAQ](/en/getting-started/seamless-energy/faq.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.catfee.io/en/getting-started/seamless-energy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.