Message Types Overview
TRON Streams provides the following message types:Block-Level Data
BlockHeader Core Fields
Witness (Super Representative) Information
TRON uses DPoS consensus mechanism with 27 Super Representatives (Witnesses) taking turns to produce blocks.
Transaction-Level Data
TransactionHeader
Result — Execution Result
Receipt — Resource Consumption
Contract
Contains contract execution details:Transfer Data
TransfersMessage provides TRON chain transfer information (Topic: tron.v1.transfers.proto).
TransfersMessage Structure
Transfer Structure
TokenInfo Structure
TRON Token Standards
TRC-10 is TRON’s unique native token standard, cheaper to create and transfer, but less flexible than TRC-20.
DEX Data
TradeEvents provides DEX trade data (Topic: tron.dex.trades), using common TradeEvent structure.
Trade Core Fields
DApp Info
DexPoolEvent - Liquidity Pools
TRON Chain Characteristics
Energy and Bandwidth Resource Model
Unlike EVM’s Gas model, TRON uses two resources:
Receipt shows usage and fees for both resources:
Witness System
BlockMessage contains Witness address, ID, and signature.
Predefined Contract Types
TRON predefines contract types for common operations:
Identified through Contract’s
Type field.
Resource Delegation
Users can delegate Energy and Bandwidth to other accounts, commonly used in the TRON ecosystem for:- Reducing user transaction costs
- DApps paying resources for users
Topic → Message Type Mapping
Code Examples
Python Example: Consume TRON DEX Trades
Monitor TRC-20 Token Events
Related Documentation
Concepts & Integration Guide
Kafka Streams integration basics
EVM Streams
EVM chain data streams
Solana Streams
Solana high-throughput data streams
WebSocket Real-time Data
WebSocket integration

