Tracks by role

This page is the entry point for eight developer tracks. Choose the track that matches your intended deliverable, then complete its reading and exercises stage by stage. This catalog is only for choosing a path; each track page is the source of truth for stage order, recommended reading, exercises, and completion criteria.

📘
How to choose

If TRON or blockchain is new to you, start with Track 0.

If you already have a specific product or role in mind, choose the track closest to that deliverable.

If you are migrating from Ethereum, read TRON vs Ethereum, then choose Track 3 or Track 4 according to your work.

Track overview

Track	Intended goal	End-to-end exercise	Core evidence to preserve
0 — Complete beginner	Establish a foundation in TRON and complete a first on-chain operation	Prepare a Shasta test account, then send and confirm one TRX transfer	Original `txID`, sender and recipient, amount, solidified result, and resource use
1 — Exchange and custodial wallet	Integrate deposits, withdrawals, and an internal ledger	Build a minimal TRX and test TRC-20 deposit/withdrawal, idempotent crediting, and reconciliation loop on Shasta	Deposit key, ledger entry, withdrawal `txID`, recovery drill, and reconciliation result
2 — Non-custodial wallet	Add TRON accounts, asset queries, and basic transfers to a wallet prototype	Restore a test account, display assets and resources, and locally sign TRX and TRC-20 transfers	Account vectors, data-to-sign summary, original `txID`, and unified transaction-state record
3 — DApp developer	Connect a contract, wallet, and frontend state	Test and deploy a library contract, then use TronLink for listing, renting, confirmation, and event synchronization	Test result, Shasta contract address, deployment and call `txID` values, source verification, and negative cases
4 — Advanced smart contract	Prepare a reproducible, tested contract candidate for review	Add reproducible builds, boundary tests, Energy assessment, and Shasta acceptance to a timed-payment contract	Source version, build configuration, tests, cost baseline, contract address, and verification result
5 — Super Representative candidate and operator	Understand SR operating responsibilities and complete a pre-launch readiness assessment	Inspect a non-producing node, design the permission and key model, and complete incident drills and readiness assessment	Node check, permission plan, monitoring and backup procedures, drill record, and readiness decision
6 — RPC and infrastructure provider	Build and validate a protected TRON API access layer	Build routing, ingress protection, failure handling, and client acceptance on Shasta, with an optional Nile event path	Service contract, route table, security configuration, monitoring record, failure drill, and client results
7 — Hardware wallet signing integration	Add an existing hardware wallet's TRON signing capability to an application	Read an account through the vendor's device interface, sign one TRX transfer on real hardware, then verify, broadcast, and confirm it on Shasta	Device and integration-component version record, account test data, solidified transaction, and failure-path tests

How to use a track

Choose the track closest to your current deliverable; you do not need to read the whole documentation site first.
Begin with stage 1 in the track overview, and open recommended reading only when the current task needs it.
Complete the exercises in one test project or isolated environment so the account, network, and example remain connected across stages.
Preserve the required txID, addresses, configuration, test results, and acceptance decisions. Sensitive material is never completion evidence.
Use each stage's entry condition and validation prompt to decide whether to proceed, then check the track's final criteria for an end-to-end result.

Shared constraints

Unless a track says otherwise, public-testnet exercises use Shasta. Track 6 uses Nile only for its self-hosted event extension and keeps those results separate from Shasta acceptance data.
A broadcast response without a reported error does not mean execution success. For every write, preserve the original txID and determine state from the receipt and solidified result.
Never put private keys, seed phrases, API keys, real Witness keys, or undisclosed vulnerability details in source, logs, screenshots, feedback, or version control.
Track prototypes and test records support learning and technical acceptance; they do not replace production architecture review, capacity validation, compliance processes, or an independent security audit.

Other roles

AI and agent developers: Start with MCP servers on TRON for chain data, wallet, DEX, lending, and infrastructure interfaces, then use Track 2, 3, or 6 as needed.
DeFi protocol developers: Begin with Track 3 or Track 4, then assess protocol integration with TRC-20 and the TRON DeFi ecosystem.
Token issuers: For fungible tokens, follow the TRC-20 issuance tutorial, which uses OpenZeppelin Contracts for TRON.
NFT issuers: Follow the TRC-721 issuance tutorial, which uses OpenZeppelin Contracts for TRON.

Related resources

Getting started — a five-minute entry point and core-concept map
Recipes — reusable procedures and code snippets
Integration overview — the integration map for wallets, exchanges, DApps, and infrastructure
API reference — entry points for FullNode, SolidityNode, TronGrid, and JSON-RPC