TRC-950: TRON Chain ID Definition
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Start by reading the proposal text in this issue alongside TIP-174 and TIP-474, which it references. Check that the chain ID derivation and the Mainnet, Shasta, and Nile values are stated consistently; done means the standalone definition and decimal values are clear and accurate.
Written by the indexing model from the issue text.
Description
tip: 950
title: TRON Chain ID Definition
author: yanghang8612
discussions-to: https://github.com/tronprotocol/tips/issues/950
status: Draft
type: Standards Track
category: TRC
created: 2026-11-19
requires: 174, 474
Simple Summary
Define the TRON chain ID, its derivation rule, and the decimal values identifying the standard TRON networks.
Abstract
The chain ID, referred to as chainId, is a non-negative integer used to identify a TRON network.
This TIP provides a standalone definition of chainId, specifies its derivation from the genesis block ID, and documents the chain IDs of Mainnet, Shasta, and Nile. All chain ID values in this TIP are expressed in decimal notation.
Motivation
TIP-174 introduced the CHAINID instruction in TVM, and TIP-474 subsequently optimized its return value.
These proposals primarily specify instruction behavior. A standalone definition of the TRON chain ID provides a common reference for wallets, SDKs, applications, and other ecosystem specifications.
Specification
The key word MUST in this document is to be interpreted as described in RFC 2119.
Chain ID
The TRON chain ID is a non-negative integer derived from the genesis block ID of a TRON network.
Its value MUST be determined as follows:
- Obtain the block ID of the genesis block at block height
0. - Extract the last four bytes of that block ID.
- Interpret those bytes as an unsigned big-endian integer.
The resulting integer is the network's chainId. Its value is between 0 and 4294967295, inclusive.
For a given genesis block ID, the derived chain ID remains constant.
Standard Network Values
| Network | Chain ID |
|---|---|
| Mainnet | 728126428 |
| Shasta | 2494104990 |
| Nile | 3448148188 |
These values follow the derivation rule specified above.
Rationale
Deriving the chain ID from the genesis block ID provides a deterministic definition consistent with TIP-474.
A standalone definition and a common decimal presentation allow ecosystem specifications and integration documentation to reference the same network values consistently.
Backwards Compatibility
This TIP defines the network identifier without changing historical or current TVM instruction behavior. Existing activation conditions remain unchanged.
No hard fork or on-chain migration is required.
Implementation
The derivation rule is based on TIP-474. This TIP establishes a reference definition and does not require changes to consensus or TVM execution.
Copyright
Copyright and related rights waived via CC0.
- Dominant language
- No language data
- Stars
- 341
- Forks
- 347
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tronprotocol/tips
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
tronprotocol/tips#945 · 8 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
tronprotocol/tips#944 · 6 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
tronprotocol/tips#941 · 5 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
tronprotocol/tips#938 · 15 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
tronprotocol/tips#937 · 7 comments ·
All issues in tronprotocol/tips
Similar issues
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
crosspoint-reader/crosspoint-reader#4535 ·
Maintainers usually reply within 1 day
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
bketelsen/pi-pocket-team#277 ·
Maintainers usually reply within 1 day
-
Wrong release linkedOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Genymobile/scrcpy#7178 ·
Maintainers usually reply within 3 days