TRON Node Connection Guide
CatFee provides high-performance TRON node infrastructure for developers, wallets, exchanges, DApps, and on-chain service providers.
With CatFee TRON nodes, you can connect to the TRON network through secure gRPC over TLS, using standard TRON protocol interfaces with low latency, high availability, and simple API-key authentication.
Overview
CatFee TRON nodes are designed for production-grade access to the TRON network.
Our service supports:
Secure gRPC over HTTP/2
TLS-encrypted connections
Standard TRON wallet and walletSolidity services
API-key authentication
Low-latency access across Asia and global regions
High availability with backend load balancingAll CatFee TRON nodes are accessed through the *.catblockchain.com domain system and use port 443 by default.
Node Endpoint
After purchasing a TRON node package, you can find your node endpoint and API key in the CatFee dashboard:
TRON Node → PackageA typical node endpoint looks like this:
Connection information:
Host
tron-demo-yourNodeId.catblockchain.com
Port
443
Protocol
gRPC over TLS
Transport
HTTP/2
Authentication Header
X-CATFEE-TOKEN: YOUR_API_KEY
Supported Services
wallet, walletSolidity
Authentication
Every request to a CatFee TRON node must include your CatFee node API key.
Use the following request header:
Replace YOUR_API_KEY with the key assigned to your node package.
Supported TRON Services
CatFee supports standard TRON gRPC services.
wallet
Used for real-time data, transaction creation, broadcasting, and querying unconfirmed or latest state
walletSolidity
Used for confirmed block data and finalized on-chain records
In general:
Both services are available through the same node host and port.
Security and TLS Requirements
CatFee nodes only accept encrypted connections.
Your client must use:
Plain-text gRPC connections are not supported.
Do not use insecure gRPC options such as:
CatFee nodes use valid CA-issued certificates, so most clients can rely on the system default trust store. No self-signed certificate is required.
Client Configuration Recommendations
For best stability, we recommend the following client settings:
TLS
Enabled
HTTP/2
Enabled
Timeout
5–10 seconds
Authentication
Pass X-CATFEE-TOKEN in request metadata
Retry Strategy
Use controlled retries with backoff
Concurrency
Keep within your package quota
If your request rate exceeds your plan limit, the node may return:
This means the request rate is too high. Reduce concurrency or upgrade your package.
cURL Example
CatFee TRON nodes use gRPC over HTTP/2 + TLS, not a REST JSON API.
This means curl can be used to test connectivity, but the response body will be protobuf binary data, not readable JSON.
The following example calls:
This method uses an empty request body.
Test GetNowBlock with cURL
Replace the following placeholders:
Run:
Example using the CatFee node domain format:
If the request is successful, you should see a response similar to:
The response will be saved to:
Because this is a protobuf binary response, it cannot be read directly as JSON with cat.
Why the Request Body Is \x00\x00\x00\x00\x00
gRPC messages include a 5-byte frame header:
For an empty request body, the gRPC frame is:
That is why the example uses:
This works for gRPC methods such as GetNowBlock, which do not require request parameters.
Recommended Tool: grpcurl
For development and debugging, CatFee recommends using grpcurl when you want readable output.
Example:
If server reflection is not enabled, provide the official TRON .proto files locally:
Common TRON gRPC Interfaces
CatFee TRON nodes support standard TRON gRPC interfaces, including but not limited to:
You can use CatFee nodes with existing TRON-compatible SDKs, services, and backend systems.
Performance and Limits
Protocol
gRPC over TLS / HTTP/2
Port
443
Authentication
X-CATFEE-TOKEN
Standard Package Limit
Default 20 req/s
Latency
Average latency under 100 ms in Asia
Availability
Load-balanced backend infrastructure
Confirmed Data
Available through walletSolidity
For higher concurrency, enterprise access, private deployment, or custom security requirements, contact the CatFee team.
FAQ
Does CatFee support plain-text gRPC?
No.
For security reasons, CatFee only supports encrypted gRPC connections over TLS. Plain-text gRPC connections will be rejected.
Do I need a custom certificate?
No.
CatFee nodes use standard CA-issued certificates. In most cases, your client can use the system default certificate trust store.
What is the difference between wallet and walletSolidity?
wallet provides access to real-time TRON node data. It is commonly used for creating transactions, broadcasting transactions, and querying latest or unconfirmed state.
walletSolidity provides confirmed on-chain data. It is commonly used for stable block data, historical transaction records, and finalized state queries.
What does HTTP 429 mean?
HTTP 429 means your request rate has exceeded your current package quota.
You can resolve this by:
Does CatFee support mutual TLS or IP whitelist access?
By default, CatFee uses one-way TLS.
For enterprise customers, CatFee can provide custom security configurations, including mutual TLS, IP whitelist access, and dedicated infrastructure.
Does CatFee support high availability?
Yes.
CatFee node domains under *.catblockchain.com are backed by multiple backend instances with automatic load balancing and redundancy.
Technical Support
For integration support, enterprise packages, higher request limits, or custom security requirements, contact CatFee:
Summary
CatFee TRON nodes provide secure, stable, and production-ready access to the TRON network.
With CatFee, developers get:
Start building on TRON with CatFee’s reliable node infrastructure.
Last updated
Was this helpful?