Community support & resources
Where to ask questions, file bugs, propose protocol changes, and follow development of the TRON network — Telegram, Discord, GitHub, the Core Devs Community Calls, and the TIP proposal process.
The TRON developer community is a globally distributed network of contributors maintaining and extending the TRON protocol, the surrounding tooling, and the DApp ecosystem. This page is the entry-point reference for where to ask questions, file issues, propose protocol changes, and follow development.
Where to get help
| You want to... | Use this |
|---|---|
| Ask a quick developer question | TRON Developers Group on Telegram |
| Discuss in real time with other builders | TRON Developers Discord |
| File a bug or feature request against java-tron | java-tron issues on GitHub |
| Propose a protocol change | TIP process — see below |
| Follow protocol-level technical discussions | Core Devs Community Call schedule |
| Read longer technical posts | TRON Medium blog |
| Long-form discussion (forum-style) | TRON DAO Forum |
Contributing code
All TRON protocol code is open source under the tronprotocol GitHub organization — java-tron (the reference node implementation), wallet-cli, TronWeb, Trident, TronBox, and others. Each repository accepts pull requests; the contribution flow is documented in each repo's CONTRIBUTING.md.
The reference java-tron contribution guide: tronprotocol/java-tron CONTRIBUTING.md.
Protocol-change governance — TIPs
Protocol-level changes (new opcodes, parameter activation, consensus rules) go through the TIP (TRON Improvement Proposal) process. The flow:
- Open a TIP issue at tronprotocol/tips/issues describing the motivation, specification, and rationale.
- Community discussion in the issue thread; technical review in Core Devs Community Calls.
- If accepted, the change is implemented in java-tron and gated behind a chain-parameter flag.
- An SR or SR Candidate submits a
ProposalCreateContractto activate the parameter on Mainnet; voting opens at the next Maintenance Period boundary. - At expiry, active-SR approvals are counted. If at least 18 active SRs have approved the proposal, the parameter is approved and takes effect at that same moment.
To submit a TIP, see the standard TIP submission process. To see what's currently under discussion, browse open TIPs.
For governance mechanics (committee, proposal lifecycle, voting thresholds), see Committee & proposals.
Core Devs Community Call
Open technical discussion among core developers, ecosystem contributors, and the broader community. Schedule, agendas, and minutes live at tronprotocol/pm — TRON Core Devs Meetings. Anyone can propose an agenda item; the meetings are open to attend.
There is also a dedicated Telegram group for the call: Core Devs Community Group.
Channels at a glance
Telegram
- TRON Developers Group — general developer discussion in English
- Core Devs Community Group — focused on the Core Devs Community Call
Discord
- TRON Developers and SRs — real-time community discussion
GitHub
- tronprotocol organization — all open-source repositories
- java-tron — reference node
- TIPs — proposal process and history
- pm — Core Devs Meetings — meeting agendas and minutes
Other channels
- TRON Medium blog — release announcements, technical deep-dives
- TRON DAO Forum — longer-form community discussion
- tron.network — entry to language- and region-specific community channels
Community conductWhen participating in any of these channels, follow the community guidelines of the platform you're on. Keep discussions respectful and constructive — the TRON community is global and welcomes contributors at every experience level.
Related resources
- Committee & proposals — how protocol changes are voted in
- Becoming a Super Representative — joining the active set
- Release announcements — historical mandatory and non-mandatory upgrades
- Security & safety on TRON — protecting users and contracts
Updated 21 days ago